eosauthority / incoming-transfer-rules
On EOS, incoming transfers can have rules applied to them. Exchanges and accounts can enforce their memo fields to stop transfers that don't enter the correct details on memo for example.
☆23Updated 2 years ago
Alternatives and similar repositories for incoming-transfer-rules:
Users that are interested in incoming-transfer-rules are comparing it to the libraries listed below
- EOS Proxy Info Contract☆28Updated 3 years ago
- EOS Enhancements Proposals - (to be moved to another location)☆12Updated 3 years ago
- Hyperion History HTTP API☆30Updated 2 years ago
- EOS Smart Contract for Block Producer Information☆25Updated 4 years ago
- ☆41Updated last year
- A nodeos out-of-band block signer in Go☆14Updated 6 years ago
- API to get EOS chain history, actions, and table information via Postgresql from the State History Plugin☆18Updated 6 years ago
- DEPRECATED: The base eos.io token contract used for eosdac based tokens☆36Updated 5 years ago
- EOSIO Specifications Repository☆40Updated 2 years ago
- EOS Plugin to check and update blacklist hash for nodeos☆15Updated 6 years ago
- Automated testing framework for EOS validation☆24Updated 6 years ago
- ☆24Updated 2 years ago
- EOS block producer heartbeat plugin to coordinate BP node status and metadata on-chain☆20Updated 5 years ago
- EOS Mechanics benchmark contracts and utilities☆34Updated last year
- Never forget claimrewards again.☆27Updated 6 years ago
- Smart contract for EOSIO to create and operate continuous liquidity pools between any pair of tokens