Choose the record type by asking what you need to preserve: shared terms, one person's statement, an independent witness, or the identity of existing content.
Agreement
An agreement contains shared terms accepted by an initiator and at least one other signing party. The parties sign the same current version. A participant can propose a change instead of accepting the current text.
Use an agreement for loans, payment arrangements, delivery promises, work terms, authorisations between people, and other shared commitments.
Contracts written via Agreebase have a 350-word limit; we believe that most day-to-day intent that needs to be captured without complex contracts can be captured adequately, and in a legally-binding way, within 350 words.
Declaration
A declaration is a single-party statement. The declarant writes and signs the record; other people can be added as witnesses. An unwitnessed declaration has one signing participant and uses one required signature method as a minimum, though additional signing methods can be completed for extra proof of identity.
Use a declaration for an attestation, statement of fact, approval, receipt, or other assertion that one person wants to preserve. For example, a declaration is useful to record that on this date, you approved something in a way whose authenticity cannot be challenged at a later date.
Unless you opt to publish the full text on-chain, Agreebase blockchain records only contain hashes, so a declaration is a way to capture intellectual property of ideas, or other "secret" information privately while still being verifiable in future by re-creating the hash yourself and comparing it to the hash on the Agreebase record.
Witnessed agreement
A witnessed agreement is an agreement with one or more additional witnesses. Witnesses sign after the main signing parties have completed their current version. A record can have at most five active witnesses.
A witness to an Agreebase agreement is attesting that they believe the parties to that agreement did in fact intend to sign it. It is up to the invited witness to confirm such intent independently. If you are invited to be a witness to an Agreebase agreement or declaration, you should contact the parties to confirm that they did indeed sign.
A witness provides an additional signed attestation. A witness is not automatically a party to the underlying obligations. If a witness declines or becomes unavailable, the initiator may be able to replace or waive that witness, depending on the current state and signing progress.
Notarization
A notarization generates and preserves a SHA-256 has for any existing content:
file: the web app hashes the file without uploading it; Agreebase receives metadata and the hash from the browser, not the file itself.text: Agreebase normalizes the supplied text, generates its SHA-256 hash, and can retain normalized text for authenticated verification. By default the text being notarized is not published on the blockchain record, but optionally can be.hash: the client supplies an existing SHA-256 digest and a label or filename. This option is only available via API or MCP.
Notarizations can have co-notarizers who sign the same content hash. They do not generate signed PDFs. Sealed notarizations expose notarization metadata and can generate a private PNG card instead. If a co-notarizer declines, the creator can complete without that person; any other invited co-notarizers must still respond. The creator can rescind the notarization while it remains pending.
Shared record properties
All record types have an AGR reference, a lifecycle status, a current version, participants, an expiry window where applicable, and privacy/publication settings. Agreements and declarations use the shared body-word limit. A notarization uses content-type-specific size and hash rules.
Choose Create and seal for agreements, declarations, and witnessed records. Choose Notarise content for an existing file, text value, or digest.