Problem and BCH usefulness
Fulcrum serves wallet queries without making each user run a full node. Its funded RPA work supports reusable payment-address clients and the associated privacy workflow. [3][4][5][7]
Fulcrum serves wallet queries without making each user run a full node. Its funded RPA work supports reusable payment-address clients and the associated privacy workflow.
Project overview & BCH-1 report · combines linked funding rounds, commitments and results. Each campaign retains its own proposal review; funding success does not establish delivery.
Recorded campaigns only; historical coverage has not been established as complete. The BCH and historical USD figures cover linked records, not lifetime project funding.
1 of 1 recorded funded campaigns priced at their own dates. 0 use archive dates rather than confirmed funding dates. Daily reference prices, not actual USD proceeds or today’s value.
Fulcrum serves wallet queries without making each user run a full node. Its funded RPA work supports reusable payment-address clients and the associated privacy workflow. [3][4][5][7]
ElectrumX-compatible servers and Rostrum are relevant indexer alternatives; BCHN is a complementary consensus backend. Fulcrum’s published RPA index and protocol 1.5.3 support provide a specific capability, not merely another server name. [3][4][5][7]
Protocol compatibility, documented operator configuration and packaged releases allow reuse across wallets and server operators. Exact operator counts, uptime and wallet-user totals were not measured. Wallet-server protocol integration and documented deployment support reach; exact operators and wallet-user counts remain unknown. [3][4][5][7]
Eligible recorded funding: 30.00000000 BCH; approximately $7,945.50 using retained historical USD reference prices. These are funding equivalents, not actual expenditure. A zero eligible subtotal with missing funding records does not mean zero development cost. Unconfirmed dates and grace-window rounds are excluded. [3][4][5][7]
RPA RPCs, initial indexing and release/configuration are evidenced. A promised performance/benchmark outcome remains only partly reconciled; most core outcomes delivered fits 8, rather than near-full 9. This is a scope judgment, not a failure inferred from a dead archive. [3][4][5][7]
About $7,945.50 in retained historical funding directly supports the released RPA capability. Reusable wallet-server infrastructure supports strong value 8, without calling it exceptionally efficient solely because the award was small. Do not attribute all lifetime Fulcrum capabilities to this award. [3][4][5][7]
Tagged releases name the campaign and explain implementation and configuration changes. Benchmark acceptance remains explicitly open. [3][4][5][7]
Assessment revision bch1-autonomous-v2-2026-11-12-applicability. Source refresh is bounded; HTTP success is not claim verification. Unavailable/JS-only sources do not erase accepted evidence. Ratings express anchored judgments, not precise measured completion percentages. Analyst simulation: primary-source claims and retained campaign evidence; independent on-chain spending, full deployment testing and matched peer-cost/usage datasets are not established. Original campaign identities and recorded completion states are preserved. Unassessed work is neither failed nor delivered. [3][4][5][7]
Extracted commitments and source-reported achievements. A passed target date or funded campaign does not establish delivery.
Tracked-item counts do not measure full scope coverage or the relative value of each outcome.
1 items not yet assessed. Missing evidence review does not establish non-delivery.
Included in score · eligible 2024-08-23
Campaign 75493d219e9a82a1 · 2024-02-23
Autonomous summary3 of 4 tracked items complete (reported, verified or explicitly presumed); 1 unassessed. These are raw counts, not economic weights or proof of full scope coverage. Eligible for this dated assessment; unknown scope is not a failed commitment.
Version 1.10.0 reports the RPA index and configurable indexing start height; published operator configuration documents activation. Source-reported implementation, not an independently rerun initial-sync test. [2][3][4]
Source target: No date statedVersion 1.11.0 reports RPA indexing performance improvements. This supports optimization delivery, but no complete campaign-specific benchmark comparison was recovered; partial evidence, not confirmed non-delivery. [2][5]
Source target: No date statedChecked 2026-11-18 · Source checked. Repository activity does not establish milestone delivery.
Profile revision 5 · updated 2026-11-11 · Initial research snapshot
Primary project page reviewed for this initial profile; descriptions are paraphrased and claims are attributed.
Extracted from Atlas campaign 75493d219e9a82a1 in snapshot 7560ba6c9105db3e11bc746c736df90f5651e17e786bb0eccf9cec30e04b321a. Historical promises are not current delivery verification.
Reopened for the locked 12 November methodology. Response SHA256 8ce843498aa559ca09b94a6b439124e8522b70d3a346820532f1f477d81284a6; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.
Reopened for the locked 12 November methodology. Response SHA256 436bf01378ee5d09963e3a7f46a81deca6b6b3c3e1e7f1a6c5022eb208f400c2; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.
Reopened for the locked 12 November methodology. Response SHA256 2a1f96b7fcd8980c27ef5a10fdee9b1f439391bda1b79b53adb1d27b1798e6c5; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.
Retained Atlas recovery/chain observation, not freshly refetched in this audit. Funding date uses claim/block timestamp, not archive discovery. Snapshot retained in the audit evidence; public explorer is the receipt reference.
Reopened for the locked 12 November methodology. Response SHA256 0eca6fb8cf32a9b39c8a5d7347d40fecdfcc511c28c36cdc37b342e689f2f07d; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.