You would have to rewrite it in Solidity/equivalent.

Yep, all the time!

Algorand recently launched support for Python smart contracts. A lot of people have had questions about learning Python, how the compiler works, and whether it's a good smart contract language. Just sharing my thoughts :)

Thanks!!

I think so, yeah. I'm going to create a new repo at some point for smart contracts that I've tested properly, are versioned, and are deployed on testnet and mainnet. Kind of like OpenZeppelin for Algorand :)

Alexander Codes So it's kind of like: Outer: Application Call ( pledge method) Inner: Deploy vault factory (inner rekey to sender & return the address) Delete vault factory contract Fund vault account

I believe it's creating a new contract on the fly. The 'vault factory' contract is ephemeral in a way... a new contract is deployed whenever the method is called, and then it's deleted in the same transaction group. The contract account remains even after the application is deleted. I think that's why you have to supply the compiled TEAL approval program and clear state programs. There's no existing application on the chain that gets called... it's creating a new one from scratch each time. I think the reference to VaultFactory.new probably just provides the the information for the ABI call (the method signature to use for encoding and decoding). As I understand it, the minimum balance requirement only needs to be satisfied by the end of the transaction group. The act of creating a vault and rekeying it is all done with inner transactions. Hope that makes sense...

I've just set it up, it's alexandercodes.algo :)

Eldar Ahmadov Agreed, and it's also a bit weird that you can't iterate over a mutable data structure directly. I would imagine that might change in future releases. In any case... I do what the compiler tells me to do :D

Alexander Codes Just to complete the Python example: a = [1, 2, 3] b = a.copy() b.pop() print(a, b) [1, 2, 3] [1, 2]