That’s currently just a piece of text, but don’t tell anybody until we decentralize 
Okay I’ll take that to mean you’re fully in control of all ICP deposited to Seers.
Why do you have hello in the repo?
Also why did you commit .vessel to github?
Also can’t seem to find the Motoko code
Hi @cyberowl, thanks for the questions.
- That’s the repository for the new frontend we’ve started developing. We’re still organizing our GitHub; however, the Motoko code is in another one.
- As for seed funders, we’re including only our NFT crowdfunders and early users. Please let us know if you have any suggestions.
Is this the one: GitHub - SeersSocial/Seers0: Repository for Seers, a web3 social network running on top of the Internet Computer
1 Like
How are you doing scaling? I only see main and State.mo where all the data seems to be stored. Is this correct? Besides the file storage not sure how scaling is done. Also I only see two here.
Also how are you doing staging testing. I don’t see any tests. Where can I find more about this?
Also why not have this as a lib?
Thank you for your questions once again!
- Our scaling approach will probably mirror that of OpenChat, where each user is assigned a separate canister with stable memory usage. Perhaps with the addition of shared canisters for users that want to save costs. Currently, we’re operating with modest memory usage and striving for simplicity as we progress with decentralization. We’re actively conducting tests on various scaling approaches to ensure the best possible user experience.
- We’re also deeply involved in the process of refactoring, generalizing, and preparing an extensive suite of tests for prediction markets. These tests will be complemented by audits and will be made available in due course. Although prediction markets code is presently disabled, anticipate their upcoming release.
- We encourage you to raise any additional concerns in the repository. This way, we can uphold the clarity of this thread by avoiding an overload of intricate details. Additionally, developers can directly provide responses to your inquiries on the repository.
- Furthermore, we will be introducing bounties to reward contributors to our repositories.
Feel free to ask if you have any more questions or require further information!
You have to be careful with that and set rate limits, any form of DDOS will drain all the cycles. I mean the cycles can be the rate limit I guess. But bots attack will add up, you might be able to detect those accounts and remove them. I know union-db is doing some good work, maybe it will be prod ready when the time comes.
Yeah refactor is a good idea. I guess you can do that when you scale the application.
Thanks! I can’t seem to find the repository that contains the canister code for Seers, can you please point me to it?
1 Like
1 Like
Hold on.
You’re now saying that Seers will create a Liquidity Pool ? For just rewarding users within the platform?
I don’t understand the economics logic of that move. But anyway, what is your other intentions with LP?
What else can people do with LP?
Will you be making the SNS yaml file available? Thanks
Yes, it will be available here: https://github.com/SeersSocial/sns/blob/main/sns.yml. You can use that one to provide initial feedback, but please note that it’s not the final version. We will make a post here when the final version becomes available, probably next week.
Looks great, good job.
1 Like
I guess this is a larger discussion with Dfinity and your early supporters but why should they be locked in a vesting period?
- controller: n2xex-iyaaa-aaaar-qaaeq-cai # Crowdfund NFT
stake_e8s: 200000000000000 # 2%
memo: 0
dissolve_delay_seconds: 2628000 # 1 month
vesting_period_seconds: 15768000 # 6 months
- controller: n2xex-iyaaa-aaaar-qaaeq-cai # Crowdfund NFT
stake_e8s: 200000000000000 # 2%
memo: 1
dissolve_delay_seconds: 2628000 # 1 month
vesting_period_seconds: 31536000 # 12 months
- controller: n2xex-iyaaa-aaaar-qaaeq-cai # Airdrop Early Users
stake_e8s: 200000000000000 # 2%
memo: 2
dissolve_delay_seconds: 2628000 # 1 month
vesting_period_seconds: 15768000 # 6 months
- controller: n2xex-iyaaa-aaaar-qaaeq-cai # Airdrop Early Users
stake_e8s: 200000000000000 # 2%
memo: 3
dissolve_delay_seconds: 2628000 # 1 month
vesting_period_seconds: 31536000 # 12 months
Isn’t it more fair to give them some liquid shares?
1 Like
Yes, that is one of the changes we will make.
1 Like
Also you do your airdrop a bit diff from Kinic, you don’t use airdrop_distribution. Did you find a better approach?
Will organize later to follow some kind of structure but you can find them all here: GitHub - cybrowl/sns-archive: sns archive - let history be the judge of decentralization init
Except for 
& 
1 Like
Good point. I think the airdrop_distribution might not be effective for us in terms of the percentage of claims. Therefore, we are considering adopting a strategy similar to Hot’s. Additionally, the airdrop will be based on contributions to Seers, such as the number of posts, etc. Now, we have come to realize that we might need to transfer some or all of it to the treasury. We will be consulting with DFINITY about this. cc @bjoernek
1 Like
Are you going to get that canister audited and blackholed. It does seem like going that route is not decentralized since the keys are in your hands. I understand that you need a canister to do that logic since it prob follows some formula in regards to your users activity. However, I think an audit of that would be great from someone outside the Seers team. Otherwise the canister can just redirect the rewards to burn addresses and then dilute the power of those users. Not saying you will do that but what if there is a bug?
3 Likes