Block a user
fix(server): added `chain_id` check and covered `check_shared_constraints` with unit tests
fix(server): added
chain_id check and covered check_shared_constraints with unit tests
Mutation Testing: Missing Test Coverage (~184 genuine gaps from 225 mutations)
feat(server): integrity envelope engine for EVM grants with HMAC verification
feat(server): implement useragent_delete_grant hard delete cleanup
Well, after some chill I though of another idea: we could just use shared_grant_id (id of evm_basic_grant) instead of grant specific id.
In this way, we would avoid writing generic invocation…
Zombie user-agent sessions can block all new client approvals
Consumed bootstrap token is not zeroized in memory
Bootstrap token comparison is not constant-time
Wallet-access revocation deletes by wallet_id instead of entry id
Integrity MAC depends on unordered SQLite row ordering
Client approval quorum differs from documented consensus model
Bootstrap token RNG seeding should be made explicit
RequestTracker allows arbitrary gaps across request flows
Integrity envelopes do not survive root key rotation