each community will probably post for a few months, earn from the ecency points system (which is built in) and then token drops happen to the community based on their points.
this means that the community's main creator or owner can earn tokens too like everyone else. then there is no issue with regulated securities.
Interesting is the metamask thing because I have written about exactly the same thing to use metamask/ EVM chain wallet as soft wallets years ago.
I really like that.
Is there some beta stuff out I can test with? Or documentation?
the basic front end will be a ecency fork/copy right?
What will be onchain and what can be stored local or on 3speak network?
I see Ceramic accounts are good to get all EVM chain frens on hive without a huge problem, that's cool.
Like Ethereum social ( i would call it for marketing reason ETH-social :D)
A solution for mass onboarding and community onboarding would be something interesting.
Like send members of a current community an sign up email or integrate it all users (local) with usernames ( maybe prefix addon) to an hive front end.
i mean something like: @did:key:app.username to make it super easy. Mostly to allow other websites to add token balances without a huge education program.
There will be a lot of flexibility between on chain and off. Both will be possible.
Ceramic accounts are basically off chain accounts to which u can attach other chains such as eth or hive.
We have built a huge ceramic indexing system that allows ceramic nodes to make content available to any platform that has the indexer installed. We are currently working on and combined hive + ceramic indexing feed so platforms can integrate off chain content and pull from the same database of content via the off chain on chain combined indexer.
Balances will be possible to add if an on chain account connects to a ceramic account
What will be onchain and what can be stored local or on 3speak network?
All offchain content will not stored on chain. There might be references on chain for indexing purposes but more TBD on this area. (specifically the light account side of the project)
Email login is very much possible. However, it requires a service that handles the email part and storing the private key of the user. Already a fair bit of services exist to this for Ethereum/others.
i mean something like: @did:key:app.username to make it super easy. Mostly to allow other websites to add token balances without a huge education program.
I'd recommend having an internal resolving within the platform that resolves an @username to did:key:etc. The did:key only accepts a public key as a value. Anything custom will need to be specified another way. We can also resolve the did:key via caip10links. Meaning you can go to @0x01234567890 and get a profile.
Thats the plan.
each community will probably post for a few months, earn from the ecency points system (which is built in) and then token drops happen to the community based on their points.
this means that the community's main creator or owner can earn tokens too like everyone else. then there is no issue with regulated securities.
tokens coming soon to this
Interesting.
What about airdrops because of some parameters?
Example:
Someone onboard an online community with X members. The online board the people coming from has already a point system.
This point system should now become the Token.
Or other parameters?
I mean I could simply ask, are those tokens customizable? :D
And will be a plug-and-play solution for it?
Because I love to ask questions, will the L2 wallets from 3speak work for onboarding mass people at a little cost with easy log in like email?
Yes to all of this. All can be built in.
The idea with the ceramic accounts is that they enable log in with meta mask initially.
You would have to check with @vaultec but there should be an easy sign up process to get a accounts at scale using email yes. All being built out
Interesting is the metamask thing because I have written about exactly the same thing to use metamask/ EVM chain wallet as soft wallets years ago.
I really like that.
Is there some beta stuff out I can test with? Or documentation?
the basic front end will be a ecency fork/copy right?
What will be onchain and what can be stored local or on 3speak network?
I see Ceramic accounts are good to get all EVM chain frens on hive without a huge problem, that's cool.
Like Ethereum social ( i would call it for marketing reason ETH-social :D)
A solution for mass onboarding and community onboarding would be something interesting.
Like send members of a current community an sign up email or integrate it all users (local) with usernames ( maybe prefix addon) to an hive front end.
i mean something like: @did:key:app.username to make it super easy. Mostly to allow other websites to add token balances without a huge education program.
Try out www.starterkitdao.com
There will be a lot of flexibility between on chain and off. Both will be possible.
Ceramic accounts are basically off chain accounts to which u can attach other chains such as eth or hive.
We have built a huge ceramic indexing system that allows ceramic nodes to make content available to any platform that has the indexer installed. We are currently working on and combined hive + ceramic indexing feed so platforms can integrate off chain content and pull from the same database of content via the off chain on chain combined indexer.
Balances will be possible to add if an on chain account connects to a ceramic account
This is the first time I'm hearing about Starter dao haha! This is really cool!
GraphQL API has a lot of useful documetation on reading data https://us-01.infra.3speak.tv/v1/graphql
As well as...
https://github.com/3speaknetwork/spk-graph-client
https://github.com/3speaknetwork/spk-indexer-node
All offchain content will not stored on chain. There might be references on chain for indexing purposes but more TBD on this area. (specifically the light account side of the project)
Email login is very much possible. However, it requires a service that handles the email part and storing the private key of the user. Already a fair bit of services exist to this for Ethereum/others.
I'd recommend having an internal resolving within the platform that resolves an @username to did:key:etc. The did:key only accepts a public key as a value. Anything custom will need to be specified another way. We can also resolve the did:key via caip10links. Meaning you can go to @0x01234567890 and get a profile.
Here is a ceramic account live on dbuzz lite https://lite.d.buzz/#/@did:key:z6MkfLNsiMYPdY3R6feCG72wVd2SV3Z1AAyomyByZukq6zV4/t/buzz/