Expand description
Interact with kimap, the onchain namespace
Modules§
- contract
- Sol structures for Kimap requests
Structs§
- Fact
- A fact log from the kimap, converted to a ‘resolved’ format using namespace data saved in the kns-indexer
- Kimap
- Helper struct for reading from the kimap.
- Mint
- A mint log from the kimap, converted to a ‘resolved’ format using namespace data saved in the kns-indexer.
- Note
- A note log from the kimap, converted to a ‘resolved’ format using namespace data saved in the kns-indexer
Enums§
- Decode
LogError - Errors that can occur when decoding a log from the kimap using
decode_mint_log()
ordecode_note_log()
.
Constants§
- KIMAP_
ADDRESS - kimap deployment address on base
- KIMAP_
CHAIN_ ID - base chain id
- KIMAP_
FIRST_ BLOCK - first block (minus one) of kimap deployment on base
- KIMAP_
ROOT_ HASH - the root hash of kimap, empty bytes32
Functions§
- decode_
fact_ log - decode_
mint_ log - Decode a mint log from the kimap into a ‘resolved’ format.
- decode_
note_ log - Decode a note log from the kimap into a ‘resolved’ format.
- namehash
- Produce a namehash from a kimap name.
- resolve_
full_ name - Given a
crate::eth::Log
(which must be a log from kimap), resolve the full name of the new entry or note. - resolve_
parent - Given a
crate::eth::Log
(which must be a log from kimap), resolve the parent name of the new entry or note. - valid_
entry - Canonical function to determine if a kimap entry is valid. This should be used whenever reading a new kimap entry from a mints query, because while most frontends will enforce these rules, it is possible to post invalid names to the kimap contract.
- valid_
fact - valid_
name - valid_
note