Our great sponsors
-
-
Jason W: @Orageux101 I am not in the research team but from my point of view: When smart contracts were first launched we supported a very limited set of opcodes. This was mainly for performance reasons. There would have been no way we could have supported full solidity. Since then that list of opcodes has grown and we made TEAL (not the AVM) turing complete. This was possible because we have also been improving our performance (which is still ongoing). Because TEAL is basically an assembler language we thought anyone could create an interpreter to it if they desired. In fact we built PyTeal to do just that. The team is also actively updating https://github.com/pzbitskiy/tealang to write contracts in JavaScript as well. Our layer 2 contracts will also use Clarity->TEAL. With the next release we will also get the ability to create payment and asset xfer transactions in the AVM similar to way you can do in Solidity contracts. After that i could easily see some converters being built.
-
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.
Related posts
- Teal?
- How a developer can contribute to community?
- 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
- I want to become a developer for Algorand. Would appreciate your tips!