-
Acceptance criteria
- [ ] implement solution for server health and disk usage alerts and monitoring
-
# Description
We already have most of what we need to access EVM data from the API (`$evmApi.telos`). However, it is desirable to have a unified store that not only centralizes access to this data bu…
-
Acceptance criteria
- [ ] Change the config.ini value for `max_transaction-time` On testnet nodes
- [ ] Change the config.ini value for `max_transaction-time` On mainnet nodes
Note:
- you CANNOT yet…
-
Acceptance criteria
- [ ] if our block production fails then we get an alert via email and/or discord on the Telos Testnet
-
On other clients a subscription to newHeads should give back the transactions as such:
```
{
"jsonrpc": "2.0",
"method": "eth_subscription",
"params": {
"subscription": "0x1",
"…
-
Acceptance criteria
- [x] Research how the resource model is implemented on antelope change. check differences in the REX, Powerup and staking models and how they were implemented
- [x] Design a reso…
-
**Describe the bug**
You can't sign any transaction using WalletConnect + Metamask in testnet. This bug affects all transactions but only this one is behaving differently because the implementation d…
-
# Add metrics to the Antelope Tools Dashboard for tEVM supporting
The tEVM improves on the EVM by implementing it’s own version of the EVM. Telos has implemented the original EVM as a smart contract o…
-
We have a smart contract deployed on Telos testnet (acc: boid) that has actions with .
it seems that after running for example:
npx @wharfkit/cli generate boid -u https://telos.testnet.boid.animus…
-
## Overview
We should remove the map because its hardcoded for telos network, showing only the block producers for Telos. Also, other chains don't necessarily want it a map.
## Acceptance Criter…