Our great sponsors
-
-
-
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.
-
For those not familiar with Solidity, there is a peculiarity in the "ABI" that makes it a bit painful to interact with other languages.
In solidity, there are types called "contracts" which are like classes in other languages. When you call a function in a different contract, the dispatch is routed using the first few bytes of the has of the signature [1].
For example, to transfer ERC-20 tokens you dispatch using `hash(transfer(address, uint256))[:4]`, meaning that you put those first four bytes at the beginning of the data that you pass to the receiving contract.
Just like the native world, this causes a problem when you try to interface between different languages. In Fe, the types have different names so this hashing scheme can't work without a translation layer. I'm not how they solve it, but from some of the issues it looks like interoperability may be a problem [2]. That's not a problem if you write all the contracts that your dApp interacts with, but as time goes on dApps interact and call into one another more and more often.
There are probably also lots of opportunities here for exploiting confusion at these boundaries, so if you're inclined and know how to use tornado you may be able to make quite a bit money off contracts that use Fe.
[1] https://docs.soliditylang.org/en/v0.8.10/abi-spec.html#funct...
[2] https://github.com/ethereum/fe/issues/592
Clarity also claims decidability. It gives up recursion and restricts looping.
https://github.com/clarity-lang/reference/blob/master/refere...
TBH a (few) hundred votes are very far from "most users are interested in this". The more popular posts have upwards of 4k votes.
https://hn.algolia.com/