Peck by twetch#14238

1NBC9L…1Yqp Key · twetch

Planning to cook something cool on BitCoin later this year🤔
Curious what yall think about cloud service providing "managed outer loop"? Like GearSV on steroids😏

What the chain says

Transaction: ff2c60f39982cc63013a090a3c455565f7acc7745c42f9de5cae227048222ae2
Block: 622 371
Time: 2020-02-16T19:53:14Z
Signer: 1NBC9L7PR7taQWdDv4opowUawb3Hmw1Yqp
App: twetch
Type: post
Content type: text/plain
Name in tx: twetch#14238

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1NBC9L7PR7taQWdDv4opowUawb3Hmw1Yqp Verified

Replies (4)

twetch#14238 6.6y

1NBC9L…1Yqp Key · twetch

Replying to@1NBC9L…1Yqp

Contracts' keys would be stored on the managed environment HW secured, and it contradicts with anarchists "not your keys - not your coins", but it's just another corecoiners' lie - evidence trail and consensus are there.

twetch#14238 6.6y

1NBC9L…1Yqp Key · twetch

Replying to@1NBC9L…1Yqp

Nevertheless, better to not store the keys, security risks are higher if we do. However, adoption and convenience shouldn't be sacrificed.

twetch#14238 6.6y

1NBC9L…1Yqp Key · twetch

Replying to@1NBC9L…1Yqp

And of course, it all lays out properly for licensed entities. If you have a "client money" permission - you will have a "custodial" cold wallet to manage them.

twetch#14238 6.6y

1NBC9L…1Yqp Key · twetch

Replying to@1NBC9L…1Yqp

And if to think about just hosting GearSV (or GearSV-like) contracts, - imagine implementing a proper escrow, or tokens exchange. And anyways - the right implementation of tokens is Tokenized (daemon replying with OP_RETURN), not GearSV.

Post by twetch#14238

Replies (4)