You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Single Owner Chunk can be pre-signed by Postage Batch before its content would be known. It allows that the Issuer who owns the postage batch attached to the SOC be a separate entity from the Poster who owns the Single Owner Chunk and posts arbitrary content. New endpoint could support this feature so that addressed envelopes can be signed with postage stamp of the node. Other details are in Book of Swarm 4.4.3 Addressed Envelops
Motivation
Cross-Chain Postage Batch Purchase workflow uses this Swarm feature which is in the design but not in implementation yet.
Implementation
The Postage Batch utilization should be updated by calling this endpoint POST /envelope/{chunkAddress}
where chunkAddress is a hexString // chunk address against which the Postage Stamp will be signed
The used postage would be the one defined in the Swarm-Postage-Batch-Id header as usual.
The endpoint must return back with an application/json response
{
issuer: hexString // Ethereum address of the postage batch owner
index: uint64 // used index of the Postage Batch
timestamp: uint64 // timestamp of the postage stamp
signature: hexString // postage stamp signature
}
that gives back all required properties for postage stamp signature verification.
The text was updated successfully, but these errors were encountered:
Summary
Single Owner Chunk can be pre-signed by Postage Batch before its content would be known. It allows that the Issuer who owns the postage batch attached to the SOC be a separate entity from the Poster who owns the Single Owner Chunk and posts arbitrary content. New endpoint could support this feature so that addressed envelopes can be signed with postage stamp of the node. Other details are in Book of Swarm 4.4.3 Addressed Envelops
Motivation
Cross-Chain Postage Batch Purchase workflow uses this Swarm feature which is in the design but not in implementation yet.
Implementation
The Postage Batch utilization should be updated by calling this endpoint
POST /envelope/{chunkAddress}
where
chunkAddress
is a hexString // chunk address against which the Postage Stamp will be signedThe used postage would be the one defined in the
Swarm-Postage-Batch-Id
header as usual.The endpoint must return back with an
application/json
responsethat gives back all required properties for postage stamp signature verification.
The text was updated successfully, but these errors were encountered: