i need a solution for logins. merchants that use blockpay(.ch) want instant transactions with shapeshift, blocktrades and other bridges. bitcoin for example is not instant, and customers do not want to stand at the cash register for 10 minutes. so, merchants pre-fund an “account” at blocktrades with a small surety amount such as $100. right now, blocktrades makes merchants sign up for an account with them with their merchant email address, password, then they have to click a link in the email for confirmation, then buy some tokens from blocktrades etc. a time consuming pain in the arse. a blockchain ID would be a WAY better solution. merchant-name.bts, merchant-name.eth, etc could be used to “login” to those Bridges for authentication and access to the surety funds that they gave to those bridge providers. if the .bts namespace for example is not active yet, can someone point me in the right direction to get it built in to blockpay, and also get these namespace ID’s accepted at the different bridge providers? please and thanx for any guidance on this endeavour…
At your Berlin presentation (i watched you on youtube), you mentioned that blockstack is chain-agnostic, just like my BlockPay project. I think your powerpoint slide even mentioned this by using our own chains we can use our own existing names on those chains, like kencode.eth, or kencode.bts etc.
Anyway, for an openauth style login to multiple sites like shapeshift and blocktrades, we need to use our blockchain id, from whatever chain the merchant prefers. So, I am a bit lost on where I should start with this.
In the BlockPay app settings, you get to choose which Bridge you want. But if those bridges are going to release the funds to the merchant instantly, then a surety amount has to be prefunded in the merchant’s account at that bridge, up to the surety amount that the merchant provides funding for. Damn, that made no sense.
Merchants do not want to setup an account with bitshares, blocktrades, gravatar, shapeshift and so on. Usernames, passwords… yuck! So, we need an api for third-party logins and auth.
Config file is done, Protobuff needs to be figured out, r/w storage operations in progress, implementing lightningDB (instead of leveldb), c-ipns datastore is in progress (with speed improvements), node is in progress, cid is usable now but needs a use case, also in progress: c-libp2p routing, c-libp2p crypto, c-libp2p network, is-domain, proquint, pin, key, merkledag, daemon, c-libp2p tcp, sctp, utp, udp, udt and open_tcp.
