Compatibility with layer 1
Tezlink supports most Tezos layer 1 features of the Seoul protocol, including:
- User account operations, such as reveals and transfers
- Smart contract operations, such as originations and calls
- Smart contract features, such as views and lazily-deserialized storage (big maps)
- Internal operations and operation batching
- Operation simulation
Some layer 1 features are unsupported because they are not relevant to a layer 2 blockchain, including:
- Baking and related operations such as attestations and delegations
- Smart Rollups and related operations such as commitments and refutations
Other layer 1 features are unsupported or partially supported because they are not yet implemented, including:
tz4addresses (BLS)- Transferring tickets
- Events
- Sapling
- Timelocks
- Global constants
- Address indexing (not yet implemented because they are not available in the target L1 protocol, which is Seoul)
Note that in order to subtract values of mutez type, one has to use the SUB_MUTEZ instruction (since the Ithaca protocol on Tezos layer 1).
Compatibility details
These tables provide details about whether specific Tezos features are supported on Tezlink.
Account types
| Account type | Supported |
|---|---|
| tz1 | ✅ |
| tz2 | ✅ |
| tz3 | ✅ |
| tz4 | 🚧 |
| KT1 | ✅ |
| sr1 | ❌ |
Supported operations
Tezlink supports operations related to user and smart contract accounts: reveals, originations, and transfers (also known as transactions). It does not support operations related to delegating, attesting, and Smart Rollups.
This table shows the complete list of kinds of Tezos operations that are supported or in progress on Tezlink. Operation kinds that are not listed in this table are not supported.
| Operation kind | Support |
|---|---|
reveal | ✅ |
transaction | ✅ |
origination | ✅ |
register_global_constant | 🚧 |
transfer_ticket | 🚧 |
Michelson instruction categories
| Instructions | Supported |
|---|---|
| Control structures | ✅ |
| Stack manipulation | ✅ |
| Arithmetic | ✅ |
| Logic | ✅ |
| Sapling | 🚧 |
| Timelocks | 🚧 |
| Other cryptography | ✅ |
| Blockchain | ✅* |
| Events | 🚧 |
| Tickets | ✅* |
| Global constants | 🚧 |
Notes:
-
Blockchain operations: Some blockchain operations related to delegation and baking are different from layer 1. For example, there is only one delegate (
tz1Kpx6wtHMc2m346MqrBJkyGFKqPPGiNueV) and it has 100% voting power. Tezlink accounts cannot change their delegate and thus theSET_DELEGATEMichelson instruction always fails. -
Events: The
EVENTMichelson instruction is allowed but the result does not appear in receipts. -
Tickets: You can deploy contracts that use tickets but ticket transfers are not displayed in operation receipts.
Fees
For now, gas consumption and fees are the same as for Tezos layer 1. However, this gas model does not match resource consumption in Tezlink, and costs can be adapted to the specificities of a layer 2 infrastructure, so they might change in the future.
RPC endpoints
The complete list of Tezlink supported RPC endpoints is at https://rpc.shadownet.tezlink.nomadic-labs.com/describe/chains/main?recurse=true and https://rpc.shadownet.tezlink.nomadic-labs.com/describe/chains/main/blocks/head?recurse=true.
You can also use the Octez client to browse and list RPC endpoints. For example, this command lists all of the top-level endpoints:
octez-client -E https://rpc.shadownet.tezlink.nomadic-labs.com rpc list
You can get further information about an endpoint by passing it to the same command, as in this example:
octez-client -E https://rpc.shadownet.tezlink.nomadic-labs.com rpc list /chains/main/blocks/head