https://github.com/kehiy/sc-collection
My smart-contract/program collection on different blockchains
https://github.com/kehiy/sc-collection
aleo aptos blockchain ethereum evm nearprotocol pactus polkadot sealevel smart-contracts snarkvm solana substrate sui ton tvm wasm
Last synced: 2 months ago
JSON representation
My smart-contract/program collection on different blockchains
- Host: GitHub
- URL: https://github.com/kehiy/sc-collection
- Owner: kehiy
- License: mit
- Created: 2024-01-15T19:15:49.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-07-18T21:13:59.000Z (10 months ago)
- Last Synced: 2024-07-30T20:55:27.811Z (10 months ago)
- Topics: aleo, aptos, blockchain, ethereum, evm, nearprotocol, pactus, polkadot, sealevel, smart-contracts, snarkvm, solana, substrate, sui, ton, tvm, wasm
- Language: Solidity
- Homepage:
- Size: 163 KB
- Stars: 10
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# sc-collection
My smart-contract/program collection on different blockchains
## Chains & Languages
### EVM
* [X] Solidity
* [ ] Fe
* [ ] Vyper### TON (TVM)
* [X] FunC
* [X] Tact
* [ ] Fift### Solana
#### Rust
* [X] solana_program
* [ ] anchor#### c
* [ ] C
### Sui (MoveVM)
* [ ] move
### Aptos (MoveVM)
* [X] move
### Aleo (snarkVM)
* [X] leo
### Plokadot (Ink/substrate/WASM)
* [ ] ink
### Near Protocol (WASM)
* [X] JavaScript
* [ ] Rust## Why?
I made this repo to keep my smart contracts here. which is used for learning, production use or referencing as examples.
Another reason that I made this repo is to get familiar with different contract models and ideas in different blockchains as a research to work on, design and develop new virtual machine/runtime environments for blockchains.## More
More resources to read and learn about smart contract engines/run-times/virtual machines:
1. [Blockchain Execution Environments Comparison](https://101blockchains.com/blockchain-execution-environments-comparison)
## Contributing
Feel free to make a PR anf update any contract if there is a typo, security issue, missing test, wrong info in docs and ...
> Note: don't forgot to use conventional commits.