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.
1NBC9L…1Yqp
1NBC9L7PR7taQWdDv4opowUawb3Hmw1Yqp
- 0 Following
- 0 Followers
- 37 Posts
Activity
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.
Nevertheless, better to not store the keys, security risks are higher if we do. However, adoption and convenience shouldn't be sacrificed.
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.
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😏
This is my first Twetch! Excited to be here 🔥