-
algokit-cli
The Algorand AlgoKit CLI is the one-stop shop tool for developers building on the Algorand network.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
use-wallet
React library for integrating multiple Algorand wallets with your decentralized applications (dApps)
-
algopytest
AlgoPytest is a framework which hides away all of the complexity and repetitiveness that comes with testing Algorand Smart Contracts.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
MakerX is our technical partner on AlgoKit, and they've been doing a stellar job. Algokit's goal is to make development extremely easy, it was built with modularity in mind because all software (languages included) ages like milk, so whatever language there will be 30 years from now can still leverage our work. We are championing beaker, we're also trying to achieve vanilla python (this is the language) which is a huge engineering effort. Smart contracts programming will never go away, we can however give ever more building blocks that compose the most common parts of smart contracts. We're evaluating formal verification, have a few options (linked in other replies) let us know what you think!
First of all congrats on becoming an AlgoBoss! Rob (MakerX's CTO) has done an excellent writeup on what the deployment experience will be on v1 release (march). We're brainstorming solutions for "grown-up" protocols to further improve the experience. To further expand on your question: a multi-sig wallet is a viable option in this case, though I would always keep mnemonics and transaction signing offline.
So in general, I like formal methods, but not currently a priority, a couple of grantees produced interesting things, like https://github.com/crytic/tealer though
For the initial release of AlgoKit we're focusing on back-end development and making sure we provide a great UX at that, we're developing a v2 roadmap and that will include a js front-end. React, Vue, Angular? Let me know which one you prefer! Whatever the outcome of the above is we want to provide a framework that generates as much as the front-end as possible and leverages tools and libraries to make that part of the development journey enjoyable
For the initial release of AlgoKit we're focusing on back-end development and making sure we provide a great UX at that, we're developing a v2 roadmap and that will include a js front-end. React, Vue, Angular? Let me know which one you prefer! Whatever the outcome of the above is we want to provide a framework that generates as much as the front-end as possible and leverages tools and libraries to make that part of the development journey enjoyable
The library we're integrating is algopytest, and Damian is currently hard at work to write documentation and examples for it. On the simulation part I think the simulate endpoint, once released, will be a game changer. There's a lot of things brewing. We will absolutely write up best practices!
Another option we're evaluating is Kavm, in the mean time we plan on having already audited smart contract and arc libraries to help get those auditing costs down
Related posts
-
Why can’t we define arrays or maps in local or global storage ?
-
My dev is angry with me for asking him to build dapp on algorand
-
I want to learn creating Smart Contracts on Algorand
-
You can now program Algorand smart contracts in (a subset of) normal Python. Spent the last several days building a tool. Bit rough but very useful until there is something better. Presenting (pre-alpha) `genpyteal`
-
need help in figuring out alogorand