- Now we try to build a open research repo for AA and related topics in 2025, replace the collection on notion.
- Join here Just open a new issue, begin to do something, then send a PR and we will review and publish your topics or any contributions 🥕.
- All contributions are welcome and will be put into review.
- This repo will publish at https://www.aastar.io/research.
- Welcome to any researcher to contribute for related topics. Just for and send a pull request(PR), we will review and publish your topics or any contributions🥕.
| Section | Link |
|---|---|
| Industry Snapshot | :link: Industry Snapshot |
| Research Blog | :link: Research Blog |
- We, AAStar, commit to build a open source infra for human digital future ❤️.
- All products are open source and public goods.
- You can try to fork and launch your own version.
- Any questions, please open an issue at https://github.com/AAStarCommunity/research/issues.
- Or something need to be discussed, please open a discussion at https://github.com/orgs/AAStarCommunity/discussions
| TypeName | Describe | Repo |
|---|---|---|
| Infra | SuperPaymaster: a universal open source paymaster contract for account abstraction. | SuperPaymaster |
| Infra | SDS: an architecture for decentralized service sponsor system. | SDSS |
| Infra | AirAccount: an open source account abstraction contract. | AirAccount |
| Infra | AirAccount-Rust-Relay: an open source relay server for AirAccount. | AirAccount-Rust-Relay |
| Infra | OpenPNTs: an open source token solution for community sustainability | OpenPNTs |
| Infra | CometENS: an open source ENS for AirAccount and SDSS. | CometENS |
| framework | HexagonWarrior: Multi OS client framework | HexagonWarrior-Tauri |
| framework | SDK and Demo: A quick Nodejs SDK and a demo to show features | AAStar_SDK |
Thanks for docsifyjs team for their powerful tool ❤️ You start to try it here:https://docsify.js.org/#/quickstart.
| Category | Emoji | Time Commitment & Activities |
|---|---|---|
| Understanding | 🧑🎓 | Dedicate over two hours weekly to stay updated on significant changes and developments in blockchain and Ethereum, such as tracking and understanding Beamchain. Share these insights through popular science articles and videos. |
| Research | 🤿 | Spend more than five hours weekly on future feature demands, requiring continuous follow-up with code and academic papers. Examples include monitoring Post-Quantum Cryptography (PQC) and lattice-based computing use cases. |
| Development | 👷♂️ | Allocate over 30 hours weekly to product design, research, and development, aiming to achieve planned roadmap milestones. This includes creating proposals and detailed documentation, along with weekly progress tracking and feature feedback. |
| Focus Area | Description |
|---|---|
| Articles 🎯 | Publish ongoing analyses and summaries on public media, covering both the "Understanding" and "Research" levels. |
| Roadmap and Milestones 🏷️ | Plan and publicize the roadmap and key milestones, ideally with usable applications for public experience. |
| Journal 📚 | Core development projects should include rigorous academic papers for arXiv and journal submissions. Initial drafts can proceed to design and iteration after peer review, with publication potentially happening later. |
| Solution 💯 | Solutions must integrate insights from academic papers, industry research, protocol visions, specific problems, and our proposed approaches. They should undergo at least three rounds of in-depth AI analysis, review, and refinement. |
| Features 🎁 | Break down solutions into specific product features that are modular and combinable within the overall product. Focus on both user experience (UX) and impact, aiming for at least three significant updates and breakthroughs in addressing problems. |
| Plan ✅ | Outline how features will be developed, tested, deployed, maintained, scaled, load-balanced, made fault-tolerant, protected against hacker attacks, and backed up/recovered. |
| Deploy 🏭 | Detail deployment and installation procedures for different environments, including service architecture and clients. This covers compatibility across various versions, hardware/software, and environments. |
| Changes 👽 | Document noteworthy changes and updates for each new feature. |