I've noticed occasional issues with Polygon, which is frustrating, and some intermittent viem/Metamask errors that I only seem to get with Polygon. I've put it down to the immaturity of the web3 stack for now but it needs to get better.
29 karma · joined November 30, 2023
I've noticed occasional issues with Polygon, which is frustrating, and some intermittent viem/Metamask errors that I only seem to get with Polygon. I've put it down to the immaturity of the web3 stack for now but it needs to get better.
Also, the data is always available on-chain and the protocol is open so other people can write an alternative ui with their own blockchain query capabilities. Like Bress.xyz does with Mirror.xyz.
Payments can be automated on-chain.
Slightly different vision and approach but both are publishing platforms. There’s plenty of room for competition in this space, I think.
Monetisation: Seedling uses direct tipping instead of NFTs. Plans for paid subscriptions to private content. Crowdsourcing will offer share of tips for investment.
Architecture: Seedling is primarily a discovery service and will allow content to be hosted on different platforms. Seedling has no backend server to deliver content.
Ideally many different hosting options should be supported.
Need to balance the freedom to publish anonymously with the risk of people claiming credit for other people’s work.
Perhaps the platform should allow any url to be published and restrict tipping to only authenticated users’ content.
Is there a reasonable long term platform fee that you would find acceptable? Say 1% or 0.1%?
As you say, there are a few programs and online services that can do similar things but they can be expensive. And you have to trust them.
Since each person's situation is different I imagine some flexibility in the unlock logic would be useful. For example, options for needing a solicitor or 2-of-n family members to hit a "he's kicked the bucket" button in their app, or send a "he's popped his clogs" email.
I had a similar idea to this using a blockchain-based private storage protocol I built called Bubble. Bubble Protocol is a general purpose private data layer for decentralised applications, like a Web3 dropbox with smart access controls. It holds data in off-chain private 'bubbles' and holds the access control logic separately on-chain in a smart contract. One smart contract per bubble. A bubble's smart contract can be custom designed for the specific application and describes the life cycle of the data in the bubble, including who can access what files, when and under what conditions.
In the case of a posthumous automation app, the smart contract would contain the unlock logic and would be kicked by the app. An off-chain bubble storage service (could be your own server or a cloud service) would store your encrypted bubble. Once unlocked, your family and friends can access and decrypt their area of the bubble.
Cheers