We are quickly approaching a milestone where another digit will be added to the block number. Assuming nothing goes wrong, block #100,000,000 is expected to be produced in the next 48 hours as of writing this. Most likely the block would already been produced by the time you are reading this.
The last time an event like this occurred was on 8 Mar 2017, 17:34:24 UTC. A brief period of network congestion will be expected as everyone will try to get their transactions included in exactly block 100M. The next time another digit will be added after block 100M (which will be block 1B) will be in another 85.6 years, provided that the year 2106 timestamp serialization problem will be fixed by then.
HiveFest 10
With the courtesy of VSC, my ticket for HiveFest 10 is secured. With less than 2 weeks to go, preparations for the event are at full gear.
Looking forward to see all of you in person again.
Contributions to VSC
Below are my contributions to go-vsc-node since my previous update in chronological order.
- GraphQL queries:
- Contract deployment script (#33)
- PR #34:
- Contract call error message in contract output
- Contract logs emitted in contract output
- GraphQL API URL option for fetching election when deploying contract
- Make contract intents available in contract execution environment
required_posting_authsfield infindTransactionquery- Contract testing utils
- PR #35:
- Fixed ledger operations not executed correctly in multiop contract calls
- Fixed indexing of transactions with posting auths only
- Fixed enforcement of
required_authsfor contract deployment
- Contract call error symbols (#38)
- PR #40:
- Contract owner made available in contract execution environment
- Intercontract state read
- Recursive intercontract calls
- Fixed contract state deletion by key
- Fixed SDK gas usage not counted in final RC usage
- RC repricing of WASM gas and SDK usage in contract calls
- Get object by key from contract state GraphQL query
- Index all contract outputs for transactions
- Fixed indexing of anchor info for offchain transactions
Witness performance
Current rank: 26th
Votes: 76,618 MVests
Voter count: 293
Producer rewards (7 days): 557.888 HP
Producer rewards (30 days): 2,408.412 HP
Missed blocks (all-time): 44
Server resource statistics
hived (v1.27.11)
block_log file size (compressed): 523 GB
block_log.artifacts file size: 2.3 GB
shared_memory.bin file size: 23 GB
HAF db
All HAF apps belong to individual schemas in a single PostgreSQL database along with data such as app state providers in the hafd schema. This section shows the sizes of each schema in the database using the following query:
SELECT schemaname,
pg_size_pretty(SUM(pg_total_relation_size(relid))) AS total_size,
pg_size_pretty(SUM(pg_table_size(relid))) AS table_size,
pg_size_pretty(SUM(pg_indexes_size(relid))) AS indexes_size
FROM pg_catalog.pg_statio_user_tables
GROUP BY schemaname;
Output
schemaname | total_size | table_size | indexes_size
------------------------------+------------+------------+--------------
hafd | 3086 GB | 2035 GB | 1050 GB
hivemind_postgrest_utilities | 32 kB | 16 kB | 16 kB
hafah_python | 16 kB | 16 kB | 0 bytes
reptracker_account_dump | 8192 bytes | 0 bytes | 8192 bytes
witstats_app | 49 MB | 30 MB | 20 MB
hafbe_bal | 77 GB | 45 GB | 32 GB
reptracker_app | 28 GB | 12 GB | 16 GB
hivemind_app | 552 GB | 280 GB | 272 GB
btracker_account_dump | 8192 bytes | 0 bytes | 8192 bytes
hafbe_app | 74 GB | 37 GB | 38 GB
hafbe_backend | 32 kB | 16 kB | 16 kB
cron | 232 kB | 136 kB | 96 kB
vsc_mainnet | 78 MB | 31 MB | 47 MB
(13 rows)
Disk usage
Compressed tablespace (including one recent snapshot): 1.9 TiB
Compression ratio for tablespace: 2.01x
Total disk usage: 2.52 TiB (71% full)