Skip to content

Fixed a typo in README.md and a typo in table.csv #379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rvagg merged 2 commits into from
May 20, 2025
Merged

Fixed a typo in README.md and a typo in table.csv #379

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d23117f
Fixed a typo in README.md and a typo in table.csv
vdods May 20, 2025
80a5b85
Merge branch 'master' into master
rvagg May 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ The process to add a new multicodec to the table is the following:

This ["first come, first assign"](https://github.com/multiformats/multicodec/pull/16#issuecomment-260146609) policy is a way to assign codes as they are most needed, without increasing the size of the table (and therefore the size of the multicodecs) too rapidly.

The first 127 bits are encoded as a single-byte varint, hence they are reserved for the most widely used multicodecs. So if you are adding your own codec to the table, you most likely would want to ask for a codec bigger than `0x80`.
The first 127 values are encoded as a single-byte varint, hence they are reserved for the most widely used multicodecs. So if you are adding your own codec to the table, you most likely would want to ask for a codec bigger than `0x80`.

Codec names should be easily convertible to constants in common programming languages using basic transformation rules (e.g. upper-case, conversion of `-` to `_`, etc.). Therefore they should contain alphanumeric characters, with the first character being alphabetic. The primary delimiter for multi-part names should be `-`, with `_` reserved for cases where a secondary delimiter is required. For example: `bls12_381-g1-pub` contains 3 parts: `bls12_381`, `g1` and `pub`, where `bls12_381` is "BLS12 381" which is not commonly written as "BLS12381" and therefore requires a secondary separator.

Expand Down
2 changes: 1 addition & 1 deletion table.csv
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -575,7 +575,7 @@ arweave-ns, namespace, 0xb29910, draft, Arwe
subspace-ns, namespace, 0xb39910, draft, Subspace Network Namespace
kumandra-ns, namespace, 0xb49910, draft, Kumandra Network Namespace
es256, varsig, 0xd01200, draft, ES256 Signature Algorithm
es284, varsig, 0xd01201, draft, ES384 Signature Algorithm
es384, varsig, 0xd01201, draft, ES384 Signature Algorithm
es512, varsig, 0xd01202, draft, ES512 Signature Algorithm
rs256, varsig, 0xd01205, draft, RS256 Signature Algorithm
es256k-msig, multisig, 0xd01300, draft, ES256K (secp256k1) Signature as Multisig
Expand Down