-
Notifications
You must be signed in to change notification settings - Fork 6
Handing off Bridge-specific tasks from Landscape #42
Comments
From conversation with @vvisigoth and @urcades:
Main integration points in Landscape:
|
Correction: the hoon side of this only generates the relevant arguments (planet name, invite code, invite address). These are sufficient for the "send invite" flow on Bridge to get started. If we want to do full transaction generation, that's not a difficult addition, all the relevant functions already exist. |
That’s what I meant, basically, but I get the distinction. We’re just passing arguments to bridge.
—
~haddef-sigwen
https://urbit.org
… On Aug 10, 2020, at 6:09 PM, Fang ***@***.***> wrote:
Right now, the API is that you can generate unsigned transactions on your Urbit ***@***.*** finished this Aug 7)
Correction: the hoon side of this only generates the relevant arguments (planet name, invite code, invite address). These are sufficient for the "send invite" flow on Bridge to get started.
If we want to do full transaction generation, that's not a difficult addition, all the relevant functions already exist.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Priority 3 because we are doing MVP Bridge integration (URL to tlon.io to handle the invite flow for hosted ships); this task is now iterating on the UX that may require the first implementation to assess. |
Closing in favour of Q4 Grid projects. |
Link Bridge-specific actions as new tabs in Bridge, passing empty transactions (see thread below).
The text was updated successfully, but these errors were encountered: