Problem and BCH usefulness
Cashonize makes native BCH token and dApp workflows accessible through a wallet interface. Its distinctive value is token metadata, identity and developer-facing functionality. [4][5][7][8]
Cashonize makes native BCH token and dApp workflows accessible through a wallet interface. Its distinctive value is token metadata, identity and developer-facing functionality.
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.
Cashonize makes native BCH token and dApp workflows accessible through a wallet interface. Its distinctive value is token metadata, identity and developer-facing functionality. [4][5][7][8]
Electron Cash offers desktop power-wallet features; Paytaca combines wallet and commerce; Selene emphasizes simple payments. Cashonize adds specialized token workflows and connection choices rather than duplicating every wallet feature. [4][5][7]
Web, desktop, APK and PWA distribution exist. No cumulative installation or active-user baseline was established; withhold a reach magnitude rather than label feature availability as 8/10 adoption. Install base and retention not established. Named dApp support establishes functionality, not unique users. [4][5][7][8]
Eligible recorded funding: 80.00000000 BCH; approximately $17,854.40 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. [4][5][7][8]
Original campaign names Google Play publication. The rendered official site explicitly says not on Play Store and explains the compliance overhead. APK/PWA availability is valuable but is not store publication. Most major rewrite and feature outcomes are documented, supporting 8; performance acceptance remains partially reconciled. [4][5][7][8]
The eligible 80 BCH award has a retained historical value of $17,854.40. The rewrite, token features and integration capabilities support strong output for this allocation, 7. Unknown active use and incomplete distribution acceptance do not substantiate exceptional 9. Do not infer zero use or total project lifetime costs. [4][5][7][8]
Public source, release notes and explicit recognition of Flipstarter support connect the implementation to community funding. Source inspection is not independent end-to-end verification. [4][5][7][8]
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. [4][5][7][8]
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.
3 items not yet assessed. Missing evidence review does not establish non-delivery.
Included in score · eligible 2024-05-27
Campaign 97d89470c5baf0f9 · 2023-11-27
Autonomous summary3 of 6 tracked items complete (reported, verified or explicitly presumed); 3 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.
Pinned source implements fiat send amounts, category-wide NFT selection/sending, identity tools, configurable IPFS/Chaingraph and rich NFT display. Creator source evidence supports the feature bundle; historical performance and store-distribution checks remain separately open. [1][2][4][3]
Source target: No date statedCurrent source contains cached lookups and batched Chaingraph queries; README documents token metadata tools. This supports implementation, but the original speed/benchmark and dynamic-import acceptance are not fully reconciled. [2][5][3]
Source target: No date statedThe official site explicitly states that the Android APK is not on the Play Store. The original Play Store distribution promise remains unfulfilled at this assessment. The APK delivery remains separately reported complete; no donor acceptance of this distribution substitution is established. [4][8]
Source target: No date statedBatching and caching are present in source. Original measured speed improvements and all dynamic metadata-import cases remain unassessed. [4]
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 97d89470c5baf0f9 in snapshot 7560ba6c9105db3e11bc746c736df90f5651e17e786bb0eccf9cec30e04b321a. Historical promises are not current delivery verification.
Read-only inspection: bchWallet, tokenItemNFT, settingsMenu, queryChainGraph and store. Implementation evidence; no transactions executed. File hashes retained in audit packet.
Reopened for the locked 12 November methodology. Response SHA256 e8c23d50267fa256537e668ee108bf194fc74cccc438ec6c4634d078da910e6a; 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 06c95e62f9536f2fa125964acc06817ff38a1a0e7e0cba6992847c80374b6b1d; 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 022ffd17026b554f42782544ad43784d1561cca31d34b94b56932ddd1a8e5060; source extract preserved in the cohort audit. Creator statements and source code are not independent deployment or financial verification.
Rendered official page reviewed; dated observation preserved in the cohort audit. Published metrics are creator-reported, not independently verified transactions or unique people.