Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Back to Big Spender
Rejected
#2 Polkawatch Decentralization Analytics Parachain Support and Continued Operation. [this proposal will not enact successfully if approved: more info below]
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
As we navigate OpenGov, we re finding new things: it seems this referendum #2 wont enact succesfully, because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin, which is the case.
We will need to resubmit this proposal:
on Treasurer track (same one)
with the call treasury.Spend (including the amount in KSM for the allocation)
The proposal has now been resubmitted here.
Hi Community,
We recently launched Polkawatch decentralization analytics on Kusama, and Nomination Pools support.
The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.
The interest peaked with a recent deplatforming event of Solana nodes by a Network operator.
We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.
Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.
On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.
The proposal has been for discussion here.
We were invited to participate in AAG#11 where an interesting discussion followed
Community feedback has been incorporated to the proposal.
You can access the detailed proposal here.
Show More
Please Log In to comment
2Comments
EJYe...YgVL
To those that supported this invalid proposal:
We have been informed that this will not pass due to invalid calls. However feel free to change your vote to NO, just in case. We have Voted NO to this proposal too.
We also appreciate if you support replacing proposal.
EJYe...YgVL
To those that supported this invalid proposal:
We have been informed that this will not pass due to invalid calls. However feel free to change your vote to NO, just in case. We have Voted NO to this proposal too.
We also appreciate if you support replacing proposal.
Discover similar proposals
#509
E5qF...tqrg
Deciding
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.
To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
