Community Pool Spend - StarShuffler dApp
rejected
Expected result
—
Turnout / Quorum
40.53% / 40.00%
9.14%
9 739 065 atom
Yes
36.64%
39 036 154 atom
No
1.81%
1 929 874 atom
Veto
52.41%
55 833 304 atom
Abstain
Details
Proposer
cosmos1hgrhzkhfjr4rku...
Total deposit
500 atom
Submit time
2025.02.24 at 23:02:02
Deposit end time
2025.03.10 at 23:03:02
Description
Proposal: Community Pool Spend - StarShuffler\n\n## Summary\nI am requesting 3300 $ATOM to build the smart-contract, relayer, and frontend for a ZK dApp for the Cosmos Hub. It will be called StarShuffler.\n\n## Details\nThis proposal would cover:\n- Creating the smart contract.\n- Developing a minimal frontend (FE) to interact with the contract.\n- Building a relayer.\n- Making the FE and relayer deployable as a Docker container for self-hosting or Akash deployments for privacy.\n\nThe milestone completion time will vary depending on the permissionless CosmWasm Hub integration timeline, which is assumed to occur mid-year. I initially asked for the funds to be proxied by the new hub leadership, but due to the sensitivity of the project’s development, the request was politely declined. However, @mag does know my identity and we have had calls, so my progress can be tracked independent of an endorsement.\n\n## Milestones\n1. Create working MVP on Juno mainnet (or testnet):\nDevelop a working MVP that includes a functional frontend, relayer, and smart contract. This milestone is contingent upon demonstrating a successful deposit and withdrawal, along with making the code open-source.\nEstimated timeline: 2 months.\n\n2. Porting the smart contract to $ATOM:\nPort the smart contract over to $ATOM and instantiate it. \nEstimated timeline: 2 weeks post permissionless CosmWasm integration onto the Hub.\n3. Integrate multi-amount pools:\nAdd support for multi-amount pools (e.g., 100 & 1000 ATOM).\nEstimated timeline: 2 weeks post milestone #2.\n\nThis effort will produce a usable app for the Hub and is relatively low-cost.\n\nI am currently designing the contract as feeless. The relayer deployment will have the option for fees for sustainability if community members want to run relayers. Having a feeless contract is motivated by both liability concerns and personal ethics.\n\nNote on Audits:\nAudits are where the serious money comes into play; I have been quoted upwards of 20k for simple audits. Therefore, I have no current plans to contract an audit, and an audit would only be conducted with community support at a later time.\n\n## Recipient\ncosmos145q97pk7hsu6zzsqtkjttlnpk90h9g6y3wzhn3\n\n## Further Discussion\nThe full forum discussions (3) are all linked here.
Votes
Voter
Answer