Handing off Bridge-specific tasks from Landscape about landscape HOT 5 CLOSED

From conversation with @vvisigoth and @urcades:

• Two phases:

  • Immediately — Bridge in its own tab
  • Phase two — Bridge is a shell around landscape

• Right now, the API is that you can generate unsigned transactions on your Urbit (@Fang- finished this Aug 7)

• App on your Urbit that creates transactions

• API creates unsigned transactions as a param into tlon.io or Bridge

Main integration points in Landscape:

• Affordance in invite where you fill in the details to the transaction to be opened in Bridge
• Automatic invite acceptance on boot
  • Couldn’t we see pending invites on boot and automatically accept it?

from landscape.

Right now, the API is that you can generate unsigned transactions on your Urbit (@Fang- 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.

from landscape.

from landscape.

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.

from landscape.

Closing in favour of Q4 Grid projects.

from landscape.