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
HELIUS DOCS: You can choose to provide your own off-chain metadata via the uri field. If no uri is specified, we will build a JSON file and upload to Arweave on your behalf. The file will adhere to the v1.0 Metaplex JSON standard. We upload to Arweave via Irys (formerly known as Bundlr).
//
Irys started out as a solution to both scale Arweave and reduce pain points experienced by developers. Our horizontal and linear scaling solutions radically increased transactions per second, from 9 TPS on Arweave directly to more than 50,000 TPS(opens in a new tab) when using Irys.
Data uploaded to Irys is given a millisecond-accurate timestamp, attributes and authorship details before being passed to Arweave for permanent storage. This information is used to create a signed receipt that can be used to verify the data's provenance at any time.
//
TLDR: We probably do not need to use the IRYS SDK as it's already used by the HELIUS API but wanted to clarify what it is , wand why it matters. There may be some edge use cases (upload biz docs) where this sdk is useful later down the line
The text was updated successfully, but these errors were encountered:
Arweave Uploads
HELIUS DOCS: You can choose to provide your own off-chain metadata via the uri field. If no uri is specified, we will build a JSON file and upload to Arweave on your behalf. The file will adhere to the v1.0 Metaplex JSON standard. We upload to Arweave via Irys (formerly known as Bundlr).
//
Irys started out as a solution to both scale Arweave and reduce pain points experienced by developers. Our horizontal and linear scaling solutions radically increased transactions per second, from 9 TPS on Arweave directly to more than 50,000 TPS(opens in a new tab) when using Irys.
Data uploaded to Irys is given a millisecond-accurate timestamp, attributes and authorship details before being passed to Arweave for permanent storage. This information is used to create a signed receipt that can be used to verify the data's provenance at any time.
//
TLDR: We probably do not need to use the IRYS SDK as it's already used by the HELIUS API but wanted to clarify what it is , wand why it matters. There may be some edge use cases (upload biz docs) where this sdk is useful later down the line
The text was updated successfully, but these errors were encountered: