Bitcoin wallet and FE integration about landscape HOT 12 CLOSED

Priority 3 because @yosoyubik availability indeterminate.

from landscape.

Removing from current Landscape sprint because it is becoming a contributor-specific project, but indeterminate timeline.

from landscape.

Added starter task specification, more to come in further task spec.

from landscape.

Will be adding screens depicting the latest state of the BTC interface work in separate posts to this issue, starting with the smaller interfaces.

from landscape.

New: BTC Interfaces in Profiles

The key elements to note here are the two placements for BTC transaction instigation:

1. A "Pay" button added to the "command list" associated with the point (Of which "Message" should be a part). This button initializes a "BTC invoicing" flow with the ship in question.
2. "Transaction creation" options in the overflow menu associated with a foreign point. These are explicit listings of what BTC transactions are possible, so "Send BTC" and "Request BTC" are listed here separately.

Notes:

1. Regarding "Pay": The word "Pay" is being intentionally deployed here, vs. "Send/Receive BTC", because we anticipate many arbitrary currencies should be able to be transacted some day. "Request" is not listed as an action, as "Message" and "Pay" are implied to be "positive"/push/send-type interactions, and we should relegate the most available actions to "positive" actions. Regardless of the word being deployed here, this button should activate a general-purpose "Invoicing Flow" where sending/receiving can be selected.
2. Both the "action list" and "overflow menu" are only displayed on profiles other than your own.

from landscape.

New: MiniProfile BTC Payments

This interface is a simple addition to the existing MiniProfile: Situated to the right of the existing "Send DM"/"New Message" button is a new button for starting a BTC transaction and invoking the "invoicing" interface.

It should be noted that this is a mirror of the "action list" we provide in foreign profiles. This is on purpose — the two should be kept intertwined.

from landscape.

BTC Transacting in Leap

These interfaces constitute a core element to this work, and could be seen as a dependency the above "Transaction Initializing" interfaces rely on, as Leap will become Landscape's core "interstitial" interface from S1.7 onward — Put simply, all of the interfaces above, when clicked, should invoke Leap as the core "invoicing" interface.

Leap itself, as a standalone "commanding" interface, should accept "Send" and "Request" as commands it can parse, which would then provide an appropriate invoicing interface.

If searching for a specific ship, I should be able to perform a keyboard based "right-click" action which I can then surface up a list of actions I can take on the ship. This list mirrors the "overflow" list provided in the profile, and should allow a pilot to search for a ship (like ~ravmel-ropdyl), initialize the "right-click" action list with Option or Alt, and select "Send BTC" or "Request BTC", which should lead into the above mentioned invoicing flows situated in Leap.

cc @g-a-v-i-n , who is the point on the S1.7 updates to Leap, to provide any additional context or thoughts!

from landscape.

In a conversation with @ixv today, I learned we'll likely be shipping our BTC invoicing interface well before Leap is developed to the degree it is in the previous reply, thus we can imagine the same forms simply being situated in our existing Landscape modals.

We should keep the above Leap interfaces in mind regardless, so the transition from modals to Leap is as smooth as possible.

from landscape.

• Some code cleaned up
• Pay interface JS in progress (waiting on urbit/bridge#534)
• Might move some elect-rs functionality into Arvo-side

from landscape.

Including the last of the primary interfaces for this project — the wallet itself.

The BTC Wallet is activated by turning on the associated toggle in System Settings:

After performing this action, the Pilot should be able to see the bitcoin wallet occupy a tile on their home screen:

Clicking into this tile for the first time, the pilot will see a "default" view for their wallet, which is obviously unset and not presenting any information. It explicitly calls out that in order to perform transactions, a peer node must be set:

The next image shows a few paths in the wallet loading/creation process. At minimum, we should afford for a pilot to load their wallet into the interface using their seed phrase, or ledger:

After a wallet has been added, a wallet visualization is added to the wallet list, finally. Clicking into the wallet shows the wallet information, the ability to send or request currency, and a list of transactions. These views are still undergoing some small design tweaks, but are essentially intact:

from landscape.

cc @ixv — these are the last views that may have been blocking progress. Let me know if there are any questions!

The last two views for navigating between wallet list and wallet view need a bit of work, but should be broadly concrete in terms of layout.

After setting a peer node, the wallet creation flows that are illustrated above at minimum should be able to support populating the wallet list with a 12-word seed/recovery phrase for the wallet. If there are other methods we need to support here, please let me know.

from landscape.

No longer Landscape purview.

from landscape.