I became interested in Sway smart contract programming language, as it is touted to be a more secure alternative to Solidity and Rust. However, after eyeing through Sway documentation, I did not find anything security specifics. What are the security-specific parts of Sway that are more innovative than other smart contract programming languages?
It is nice to see good progress on smart contract security. To continue on this topic of Fuel (not Sway), I assume any asset (or token) does not suffer the widely spread approve() and message signing issues Ethereum is enjoying? This is a part of security that sits between the chair and the keyboard and it seems poor wallet smart contract UX is a good way to have your apes running back to the forest.
Will the user interaction with smart contracts be safer? Any tricks Fuel does to accomplish this?
Since the UTXO model allows all tokens on Fuel to be native assets, the approve/transferFrom mechanism is unnecessary; any token can be forwarded with a call. The #[payable] annotation also help avoid any errors here.