Paid integration pilots
Sourced blockchain answers for your users.
Bring sourced blockchain answers into your help center, documentation or support assistant. Start with a paid pilot for one workflow, built around the questions your users need answered.
A proposed first pilot
Sourced release and feature answers inside your existing help or learning experience. This is the scope we would start from and adjust with you.
- Audience
- Readers of one team’s help center or learning pages, for example a wallet’s, an explorer’s or an ecosystem foundation’s.
- Where it appears
- One surface you already run, such as a help-center answer panel, a docs widget or a support assistant, connected to the read-only iKnow Blockchain service.
- Questions
- An agreed list of release and feature questions about the chains you choose, such as “Is this upgrade live?” or “Does this chain support atomic swaps?”
- Each answer shows
- A short answer, the stage the evidence supports, the source, and the date it was last reviewed.
- When it is not established
- It says so plainly, as “Structured assessment pending” or “Unknown” with the reason, and never shows an unavailable lookup as zero or as an empty success.
- Limits
- Read-only: no wallet keys, transactions or investment advice. It answers only what the public catalogue covers, and the research stays public and the same for every chain.
- Delivered
- The working integration, the tested question set with its results, documentation for your team, and a short review of what worked.
- Who maintains what
- The data and sources follow the public catalogue’s recheck deadlines, the same for every chain. Your team owns where and how answers appear in your product. Hosting, monitoring and support after the pilot would be agreed separately.
What a reader would see
A prototype built from records already published on this site: one release question and two feature questions, including one the review has not established. It shows the data a pilot would use; it is not a deployed customer integration.
Prototype · a real record
What changed on IoTeX, and is it live?
IoTeX released node version 2.5.0, required before mainnet block 53,533,081 (estimated 19 October 2026 02:00 UTC, moved from an earlier schedule for 8 October).
- Activation
- Scheduled for mainnet block 53,533,081 (estimated 2026-10-19); not yet active at review
- Source
- IoTeX (GitHub) — iotex-core v2.5.0 release (external site)
- Reviewed
- Reviewed Sep 29, 2026 Next review due Oct 9, 2026, 12:00 UTC.
Full record, with dates and all 4 sources
Prototype · a real record
Does IoTeX support authenticated data publication?
Authenticated data publication: built into the protocol.
- Detail
- Since the Vanuatu hard fork (v2.1.0, December 2024) blob transactions carry data whose commitments the chain records in the transaction; nodes serve the blob data through the…
- Source
- IoTeX Documentation — Blob Transactions (EIP-4844) (external site)
- Reviewed
- Reviewed Sep 29, 2026 Next review due Mar 29, 2027.
Prototype · a real record
Does IoTeX support account abstraction?
Structured assessment pending. The shared review has not assessed this feature for any chain yet; that does not mean it is absent.
- Source
- Not assessed yet
- Reviewed
- Not assessed yet
Ongoing hosting, maintenance and support
After a pilot, we can discuss a separate paid agreement for hosting, maintenance or support for your integration. Scope, responsibilities, term and price are agreed in writing. Ongoing services are included only when the agreement specifies them.
- Hosting capacity sized to your usage.
- Monitoring of the integration.
- Keeping it compatible as the service changes.
- Technical support within agreed limits.
What stays public and free
- The catalogue of all 151 chains, the evidence standard and every published record.
- Free access to the iKnow Blockchain connection for individuals (for now, accounts on its access list; opening it to every signed-in account is the next step).
- Free error reports and the public corrections log.
Who it may help
Education and developer-relations teams, wallets, block explorers and AI applications that want answers their users can check. The service is read-only: it never holds wallet keys or makes transactions, and it gives no investment advice.
How scope and price are agreed
Tell us the workflow you have in mind. If a pilot looks like a fit, we agree its scope, schedule, support limits and price in writing before any work starts. There are no published plans or price lists.
Discuss a paid pilot
Tell us who will use it, where answers should appear and which blockchain questions they need help with. That gives us a starting point for defining the scope, timing and price.
Email [email protected] or use the prepared message below. The button opens your email app; nothing is sent until you send it there.