-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enroll select projects with tea.xyz #5
Comments
A couple of weeks ago, I attempted to complete 1.3 (stake the registered projects from the projects' treasury). Today, I can confirm that inflect did get staked: I'm pretty sure I'd tried to do the same with configparser, but it was still showing the initial balance of 10,000, so I re-processed the staking and it now shows half-staked (deducted from the treasury but not yet showing in the bug bounty): I've also succeeded in staking keyring, but not the correct one. There are two keyrings on my account and I staked the non-PyPI one: Today I also requested to stake keyring (PyPI) and it's in the same state as configparser: Hopefully keyring and configparser show the staking in the bug bounty pool soon. |
configparser and keyring have successfully staked: you can always copy the address of the project (thing below the name) and search on sepolia.basescan to confirm a txn wen through. are they still not showing you a 0 value in the BBP? |
Yes! Both now show 2,500 in the BBP. Thanks! |
Today I had the AMA with Max and will add that to my twitter account once I have the link. |
I've posted this thread on Twitter for milestone 3.1 (including a call to action for fellow maintainers for half of 2.1). |
I've been approach by the tea project to consider enrolling select projects (configparser, inflect, keyring) with tea. I've signed an agreement to do just that and this issue tracks the milestones and steps.
Milestone 1
testnet. On-chain data will be utilised to confirm the completion of this milestone task.
Milestone 2
Milestone 3
by the tea Protocol incentivized testnet.
The text was updated successfully, but these errors were encountered: