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.
#62 To 0xTaylor for security related reports & community founding
Dear community,
This referendum is two fold, it seeks to grant 0xTaylor a tip of 8 KSM but also tests OpenGov to see if it protects against spending more than the track allowance when using multiple transactions.
0xTaylor is a popular actor within the ecosystem known for his input with security exploit related matters. It is through his efforts that a blacklist was developed on Polkassembly, thus preventing users from applying usernames like Admin
or Administrator
which could otherwise be misleading. He also reported Hasura GQL endpoint
exploits to various teams that utilize the service, an example of which can be found here. 0xTaylor is also known for his input within the ChaosDAO and WagMedia communities members of which have endorsed his receipt of a tip.
On the note of security, I took this as an opportunity to test the coding of OpenGov with regards to multiple spends within a single batched transaction. This proposal seeks to spend 16 KSM in two batches of 8 KSM. The first and 'guaranteed' execution being made to 0xTaylor
, in the unlikely event that there is a bug then another 8 KSM would be awarded to an account for Public Kusama Staking Rewards Payout BOT.
If the second extrinsic executes then maximum spend per track would essentially be Max spend
* Number of transactions that can be fit within a batch
.
Regards,
Show More
Thank-you for the clear introductory sentence summarizing your intention.
You have my support.
Voted Aye
I'm in full support of Taylor so I vote Aye ! I've known him since 2021 and he's been doing a lot of good cybersecurity work for the ecosystem. He found bugs and reported them and actively engaged with parachain teams to inform them of these issues. He also shares cool security tips from time to time in the PolkaHaus community
Taylor is a great watchdog in the ecosystem. This has my vote.
0xTaylor spends a lot of his time and resources to better the whole ecosystem. Absolutely!
I would like to say I really appreciate Paradox and the kind words those that know me have shared on my behalf. As well as those who have voted in approval for this Tip referenda. I am even more excited to be used as the Guinea pig in this test-case to see if Paradox can surface a potential issue.
Voted Aye
Findings were posted here
Discover similar proposals
Remove Gabe from the fellowship
See More
Fellowship Admin
Fellowship Admin
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.
Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.
TENETS (extract from the fellowship manifesto)
"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.
(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"
See More
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
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