syntax = "proto3"; package neo.fs.v2.refs; option go_package = "git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/refs/grpc;refs"; option csharp_namespace = "Neo.FileStorage.API.Refs"; // Objects in NeoFS are addressed by their ContainerID and ObjectID. // // String presentation of `Address` is a concatenation of string encoded // `ContainerID` and `ObjectID` delimited by '/' character. message Address { // Container identifier ContainerID container_id = 1 [json_name = "containerID"]; // Object identifier ObjectID object_id = 2 [json_name = "objectID"]; } // NeoFS Object unique identifier. Objects are immutable and content-addressed. // It means `ObjectID` will change if the `header` or the `payload` changes. // // `ObjectID` is a 32 byte long // [SHA256](https://csrc.nist.gov/publications/detail/fips/180/4/final) hash of // the object's `header` field, which, in it's turn, contains the hash of the object's // payload. // // String presentation is a // [base58](https://tools.ietf.org/html/draft-msporny-base58-02) encoded string. // // JSON value will be data encoded as a string using standard base64 // encoding with paddings. Either // [standard](https://tools.ietf.org/html/rfc4648#section-4) or // [URL-safe](https://tools.ietf.org/html/rfc4648#section-5) base64 encoding // with/without paddings are accepted. message ObjectID { // Object identifier in a binary format bytes value = 1 [json_name = "value"]; } // NeoFS container identifier. Container structures are immutable and // content-addressed. // // `ContainerID` is a 32 byte long // [SHA256](https://csrc.nist.gov/publications/detail/fips/180/4/final) hash of // stable-marshalled container message. // // String presentation is a // [base58](https://tools.ietf.org/html/draft-msporny-base58-02) encoded string. // // JSON value will be data encoded as a string using standard base64 // encoding with paddings. Either // [standard](https://tools.ietf.org/html/rfc4648#section-4) or // [URL-safe](https://tools.ietf.org/html/rfc4648#section-5) base64 encoding // with/without paddings are accepted. message ContainerID { // Container identifier in a binary format. bytes value = 1 [json_name = "value"]; } // `OwnerID` is a derivative of a user's main public key. The transformation // algorithm is the same as for Neo3 wallet addresses. Neo3 wallet address can // be directly used as `OwnerID`. // // `OwnerID` is a 25 bytes sequence starting with Neo version prefix byte // followed by 20 bytes of ScrptHash and 4 bytes of checksum. // // String presentation is a [Base58 // Check](https://en.bitcoin.it/wiki/Base58Check_encoding) Encoded string. // // JSON value will be data encoded as a string using standard base64 // encoding with paddings. Either // [standard](https://tools.ietf.org/html/rfc4648#section-4) or // [URL-safe](https://tools.ietf.org/html/rfc4648#section-5) base64 encoding // with/without paddings are accepted. message OwnerID { // Identifier of the container owner in a binary format bytes value = 1 [json_name = "value"]; } // API version used by a node. // // String presentation is a Semantic Versioning 2.0.0 compatible version string // with 'v' prefix. i.e. `vX.Y`, where `X` is the major number, `Y` is the minor number. message Version { // Major API version uint32 major = 1 [json_name = "major"]; // Minor API version uint32 minor = 2 [json_name = "minor"]; } // Signature of something in NeoFS. message Signature { // Public key used for signing bytes key = 1 [json_name = "key"]; // Signature bytes sign = 2 [json_name = "signature"]; // Scheme contains digital signature scheme identifier SignatureScheme scheme = 3 [json_name = "scheme"]; } // Signature scheme describes digital signing scheme used for (key, signature) pair. enum SignatureScheme { // ECDSA with SHA-512 hashing (FIPS 186-3) ECDSA_SHA512 = 0; // Deterministic ECDSA with SHA-256 hashing (RFC 6979) ECDSA_RFC6979_SHA256 = 1; // Deterministic ECDSA with SHA-256 hashing using WalletConnect API. // Here the algorithm is the same, but the message format differs. ECDSA_RFC6979_SHA256_WALLET_CONNECT = 2; } // RFC 6979 signature. message SignatureRFC6979 { // Public key used for signing bytes key = 1 [json_name = "key"]; // Deterministic ECDSA with SHA-256 hashing bytes sign = 2 [json_name = "signature"]; } // Checksum algorithm type. enum ChecksumType { // Unknown. Not used CHECKSUM_TYPE_UNSPECIFIED = 0; // Tillich-Zemor homomorphic hash function TZ = 1; // SHA-256 SHA256 = 2; } // Checksum message. // Depending on checksum algorithm type, the string presentation may vary: // // * TZ \ // Hex encoded string without `0x` prefix // * SHA256 \ // Hex encoded string without `0x` prefix message Checksum { // Checksum algorithm type ChecksumType type = 1 [json_name = "type"]; // Checksum itself bytes sum = 2 [json_name = "sum"]; }