Interact with NEAR blockchain from web frontend

[hanfel-dovned]

See #11. The relay server Gall agent will need to interact with the .urbit account issuing smart contract on the NEAR blockchain. I'm guessing this will be done with an Iris http request to an RPC node.

Since this smart contract doesn't exist yet, for the time being, let's see if we can create a new .near account and save its private key to a Gall agent, or maybe just ~& it with a thread. This issue is just to figure out the ergonomics around making smart contract calls from Urbit. (%eth-watcher might be a good place to look for this; ~littel-wolfur is a good person to ask about that.)

EDIT: On the other hand, thanks to Auth Server, we can likely get Urbit ID authentication without having to build this relay server as a Gall agent. This means that we'd be able use pre-existing JS libraries to do contract calls, as well as not have to ask the Near Foundation to maintain an Urbit app.

With this in mind, I'm renaming this issue from "Interact with NEAR blockchain from Gall agent" to "Interact with NEAR blockchain from web frontend". This will likely be a stepping stone to doing this from a node.js server.

[hanfel-dovned]

See comment on #13.

[hanfel-dovned]

https://docs.near.org/develop/integrate/frontend

[hanfel-dovned]

This issue isn't very well-specified and makes too many assumptions about how we'll be structuring the .urbit account granting server. Namely, it assumes that the relay server will be a single Gall agent running on a star that makes permissioned smart contract calls; the problem with this is that we don't want to store highly valuable keys on Urbit until Urbit is more secure.

So we'll either need a web server in the flow anyway to store the keys (in which case there won't be any smart contract calls happening from within a Gall agent), or we'll do something big-brained with Ames (in which case we won't need a relay server at all). Closing this.