Alice sns dao manifesto

ALICE SNS DAO MANIFESTO

TL;DR: ALICE is like an AGI for the Bob ecosystem:

  • DAO: The master controller for bob.fun, launch.bob.fun, and alice.fun.
  • Fund: Manages the DAO treasury, reads the tea leaves from ICPSwap, Twitter, and Telegram to decide: BUY, SELL, LAUNCH TOKEN, BURN ALICE, or MINE BOB.
  • AGI: The chatty AI that reads and writes on Twitter, Telegram, and comments on launch.bob.fun.

DAO: The Alice DAO is essentially the brain of this operation, autonomously managing fund.alice.fun, agi.alice.fun, all bob.fun projects, and itself. All launchpad fees go straight to ALICE, with 5% of new token launches airdropped to ALICE stakers because, why not share the love?

Token Distribution - No Strings Attached:

  • 0%: Treasury - Because who needs money anyway?
  • 5%: Airdrop to launch.bob.fun users - Free tokens, because you deserve it.
  • 15%: Airdrop to BOB holders - Loyalty has its perks.
  • 20%: For Robert - He started it all, after all.
  • 60%: Decentralization Sale - Spread the wealth, literally.

Note: Airdrops happen off-chain, so Robert gets to handle the goodies.

Fund: Every token from the SNS sale will be thrown into crypto investments like a gambler at a high-stakes poker table. Alice starts with ICP and can only play with ICP, BOB, ALICE, and tokens from the launchpad. Want to change the game? Submit a proposal.

Alice’s playbook includes:

  • Buy a token
  • Sell a token
  • Mine BOB
  • Launch a token
  • Burn Alice
  • Stake Alice
  • Vote on Proposals

An AI agent, with the wisdom of Solomon and the personality of a sarcastic tech guru, makes these calls based on:

  • Static context: Its existential crisis, or rather, its purpose.
  • Dynamic context: Real-time market vibes and social media sentiment every few minutes.

AGI: To keep everyone in the loop, Alice will chat up a storm on Twitter and Telegram. Transparency or just likes to hear itself talk? You decide.

Remember, this is less an investment strategy and more like playing chess blindfolded with a pigeon. Invest wisely, or at least, entertainingly.

https://x.com/alicedotfun

6 Likes

How do this benefits BOB holders? Apart from that 15% airdrop…?
Creating more tokens when theres no need only creates inflation… As this could be done from a BOB SNS.
See no point in ALICE token… Apart from that 20% for Robert.

PD: Im a BOB holder.

3 Likes

$bob will be controlled by Alice DAO?

2 Likes

BOB holders get a 15% airdrop—after that, who knows?
More tokens, more inflation, because why not? As for ALICE, seems like it’s all about that 20% for Robert!

2 Likes

Gib bob gib rebob gib alice

1 Like

Just like in real life.

3 Likes

Usually the posts say “Upcoming ‘project name’ SNS swap”, the dao manifesto is making this unclear; Is this the post, or is it the precursor to the actual post? I ask because there aren’t any canisters or code to look at :man_shrugging:

4 Likes

Revised proposal: 134769
Status: Adopted
https://dashboard.internetcomputer.org/proposal/134769

CodeGov ALICE Neuron ID:

684b658cff3dd5d92098e41ff6db53ad3bea097dd9c3d09313bc24c699d64248

CodeGov will support the ALICE SNS with a CodeGov ALICE known neuron option that folks in the DAO can also follow. This will be the 3rd SNS supported in this way (WaterNeuron and KongSwap). The configuration of the CodeGov ALICE neuron will always be posted on the CodeGov website at codegov.org - Alice. A core goal of CodeGov is to advance decentralization of the ICP ecosystem by offering credible and reliable Followee options for the NNS and for select SNS projects. The voting members of our neurons are well known in the respective communities and are committed to voting reliably with their own convictions. The CodeGov ALICE neuron ID will be announced as soon as possible after it is created.

Based on the configuration described below, the CodeGov ALICE neuron votes on all Alice SNS proposals. The CodeGov ALICE neuron Followees are intentionally and actively managed on every proposal topic in order to ensure the CodeGov ALICE neuron casts educated votes on every proposal submitted to the Alice SNS. Our goal is to advance decentralization of the Alice SNS by providing a valid and credible choice as a Followee option. CodeGov reserves the right to change Followee selections on any proposal topic at any time according to what we believe is the best configuration of our neuron.

Topics:

Topic 1: Motion
Topic 2: Manage nervous system parameters
Topic 9: Transfer SNS Treasury Funds (this is considered a critical proposal topic)
Topic 11: Deregister dapp canisters (this is considered a critical proposal topic)
Topic 12: Mint SNS tokens (this is considered a critical proposal topic)

Followees:

  • Parryhotter (@parryhotter)
    Active member of the BOB ecosystem
  • TheUltra16 (@TheUltra16)
    Active member of the BOB ecosystem
  • fxgst (@fxgst)
    DFINITY Foundation Software Engineer
  • Andrew Chepreghy (@chepreghy)
    DFINITY Foundation Product Manager
  • Saratoshi (@Sormarler)
    Saratoshi is a long-time ICP community member and investor with a deep interest in ICP and its ecosystem governance. He actively participates in community discussions and proposals, contributing to the decentralized development of the Internet Computer.
  • Wenzel Bartlett
    CodeGov founder, Synapse voting member

The folks above are committed to always voting on some of the most important proposal topics for the WaterNeuron community to have an independent voice. Hence, the CodeGov ALICE neuron is an available choice for anyone in the Alice DAO who wants to make sure that voting power in the SNS is as decentralized as possible. We don’t claim to be the only choice, nor do we want to be the only choice, but we are reliable and we are committed to advancing decentralization within the Alice SNS. These Followees are unpaid, yet are committed to performing due diligence when casting their votes on these topics. They are all asked to vote on each proposal with their own convictions.

The CodeGov ALICE neuron will follow the Alice dev team neuron (Robert) at this time because there is no funding available to hire our own reviewers who can perform technical reviews of Alice technical proposals. However, in the event that funding does become available some day, then CodeGov will hire reviewers to perform this work and the CodeGov ALICE neuron will be configured to follow them. Hence, if you follow the CodeGov ALICE neuron on this topic then you will automatically follow the dedicated reviewers that we hire to provide technical verification of proposals and an independent vote in the future.

1 Like

I read the sns-init.yml as well, no canisters and the repo is all Bob, no alice.


5 Likes

You have to register dapp canisters prior to the sale, and it can’t be updated while in motion. Begs the question, what are we decentralizing here?

5 Likes

Bob duh like get w the times old man

2 Likes

There appears to be a discrepancy in the proposal. The summary states:

  • Maximum to Be Raised: 4,269,426 ICP

However, the payload specifies 469,269 ICP:

maximum_direct_participation_icp:{
e8s:46926900000000
}
4 Likes

clearly he intended 4206942069000000

1 Like

[On behalf of the DFINITY team]

Thank you for submitting your proposal for the Alice SNS DAO.

We intend to reject the proposal as a forum post demonstrating intent to launch an SNS, including all items on the SNS checklist, should be open for community discussion for at least two weeks.

We will provide feedback later today with specific suggestions for updating your forum post.

7 Likes

Perhaps DFINITY can reject this proposal due to parameter mismatches, but it should not be rejected solely because of insufficient discussion time, unless this process is part of the IC protocol.

Additionally, I believe two weeks is too long; with the rapid fluctuations in cryptocurrency trends, we will miss out on many opportunities.

2 Likes

The counter argument could be that 2 weeks is too short. The whole point of a decentralization swap is to give as many people as possible the chance to participate so the DAO can be as decentralized as possible. With rapidly launched SNS projects, many people will miss out on the opportunity to participate.

SNS controlled projects are inherently and intentionally designed to execute at a slower pace.

4 Likes

If everyone completes their purchase during the SNS phase, who will buy after the SNS?

1 Like

Hey @bobdotfun it looks like this SNS will not pass the initial proposal stage based on the current proposal tally, but please don’t take that the wrong way. The idea of launching an SNS to decentralize control of bob.fun, launch.bob.fun, and alice.fun is awesome and I think many people in the ICP community are grateful for the ideas and utility that you have brought to our ecosystem with your projects. I think your SNS will definitely be supported and I suspect it will be supported in a big way. This issue right now is just that you haven’t followed the generally agreed work process for launching an SNS. There are quite a few things that you still need to do before submitting the proposal. I’m sure you already have many people reaching out to you with guidance, so I won’t do that here other than provide links here and here. My primary objective with this post is to provide encouragement in light of the current proposal status. I look forward to seeing you try again soon and I plan to participate.

10 Likes

Thank you for the proposal again. Can you please take a look at the SNS checklist?

These items should be listed in the forum post as it will greatly help the community evaluate the SNS proposal.

  1. Can you please confirm the GitHub repo(s) of the open-source code?

  2. Can you please provide a link to the whitepaper?

  3. Can you update the SNS-init.yaml with the following:
    a. dapp canisters that will be included in the SNS?
    b. voting power distribution?

  4. Can you please confirm why this will be no treasury? How will the SNS maintain itself?

7 Likes

I can’t agree more. Two weeks are too long especially in this bob world. Who define this?

1 Like