www.cashaccount.info
Open in
urlscan Pro
185.36.149.218
Public Scan
URL:
https://www.cashaccount.info/
Submission: On August 10 via automatic, source certstream-suspicious — Scanned from DE
Submission: On August 10 via automatic, source certstream-suspicious — Scanned from DE
Form analysis
2 forms found in the DOM<form onsubmit="return false;">
<!-- Step 1: You choose a name and BIP-47 payment code -->
<fieldset id="fieldset_create_transaction" class="active">
<legend align="center">Choose account name</legend>
<label>
<span>Enter your name:</span>
<input id="alias_name" type="text" placeholder="SatoshiNakamoto" pattern="\w{1,99}" required="" autocomplete="off">
</label>
<label>
<span>Enter your <b style="border-bottom: 0.05rem dashed rgba(0, 0, 0, 0.55); font-style: italic;" title="an address, payment code or stealth keypair">payment information</b>:</span>
<textarea id="alias_payload" placeholder="qqgekzvw96vq5g57zwdfa5q6g609rrn0ycp33uc325" rows="5" name="" type=""></textarea>
</label>
<label>
<button id="alias_create_transaction" disabled="">Create Register Transaction</button>
</label>
</fieldset>
<!-- Step 2: We create an on-chain transaction -->
<fieldset id="fieldset_broadcast_transaction" class="inactive">
<legend align="center">Broadcast transaction</legend>
<ul>
<li><span>Protocol</span><i title="OP_RETURN">6A</i> <i title="push 4 bytes">04</i> <i title="Cash Account">01010101</i></li>
<li><span>Account Name</span><span><i id="alias_name_length" title="push 15 bytes">0F</i> <b id="alias_name_hex" title="UTF-8 encoded name from: SatoshiNakamoto">5361746F7368694E616B616D6F746F</b></span></li>
<li><span>Payment
Data</span><span><i id="alias_payload_length" title="Push 21 bytes">15</i> <i id="alias_payload_type" title="Type: Key Hash">01</i> <b id="alias_payload_hex" title="Decoded Key Hash from: qqgekzvw96vq5g57zwdfa5q6g609rrn0ycp33uc325">119B098E2E980A229E139A9ED01A469E518E6F26</b></span>
</li>
</ul>
<label>
<button id="alias_broadcast_transaction" disabled="">Broadcast Register Transaction</button>
</label>
</fieldset>
<!-- Step 3: When a block is mined, define the alias -->
<fieldset id="fieldset_confirm_transaction" class="inactive">
<legend align="center">Wait for block inclusion</legend>
<ul>
<li><span>Expected Identifier</span><i id="alias_name_predication" title="Name">SatoshiNakamoto</i>#<i id="alias_expected_blockheight" title="Calculated from the blockheight of the next block.">567890;</i></li>
<li><span>Transaction Hash</span><span><i id="alias_transaction_hash" title="Transaction Hash">7e5a1bda26244042d03d679b38f90cb83fd8a3507de3123da66ffdf934a1b241</i></span></li>
<li><span>Status</span><span><i id="alias_registration_status" title="Not yet created">None</i><!--, <i id='alias_registration_status_collision' title='No competing registration for this name in the mempool'>Collision-Free</i>--></span></li>
</ul>
<label>
<button id="alias_lookup_transaction" onclick="website.lookup_identifier(this.innerHTML.substring(8), 199); window.location = '#lookup';" disabled="">Lookup: SatoshiNakamoto</button>
</label>
</fieldset>
</form>
<form onsubmit="website.lookup_identifier(null, 999); return false;">
<fieldset>
<legend>Look up Cash Account</legend>
<input id="lookup_search_string" name="" type="text" placeholder="Search for account...">
<input type="submit" value="search">
<ul id="result_list"></ul>
</fieldset>
</form>
Text Content
Introduction Registration Lookup Wallets Testimonies » Cash Accounts Bitcoin Cash needs an alias/address system that is designed to meet the expectations of normal users. Cash Accounts allows for human readable account names that are easy to share in conversation. by Jonathan#100; and Robbot#102; Choose account name Enter your name: Enter your payment information: Create Register Transaction Broadcast transaction * Protocol6A 04 01010101 * Account Name0F 5361746F7368694E616B616D6F746F * Payment Data15 01 119B098E2E980A229E139A9ED01A469E518E6F26 Broadcast Register Transaction Wait for block inclusion * Expected IdentifierSatoshiNakamoto#567890; * Transaction Hash7e5a1bda26244042d03d679b38f90cb83fd8a3507de3123da66ffdf934a1b241 * StatusNone Lookup: SatoshiNakamoto Look up Cash Account * Fully supported * Looking in to it * Working on reusable addresses * Requested on Github * Confirmed on twitter * Fully supported * Evaluating compatibility with FIO * Fully supported * Supports sending to cash accounts * Fully supported * Fully supported * Accepted in chat, but low priority * Josh Ellithorpe Senior Engineer, Coinbase Having an on chain, decentralized system with human readable identifiers is a major usability win for new users and pro crypto users alike! * Vin Armani CEO, CoinText Cash Accounts is a huge step forward in making Bitcoin truly usable as peer-to-peer electronic cash for the world. * Jonathan Silverblood Jack-of-all-trades Using payment codes with Cash Accounts gets you an account name that is secure, decentralized and meaningful, effectively solving Zookos trillemma. * Mark Lundeberg Developer, Simple Ledger Protocol Solves the squatter problem by appending a short number which is an inconvenience, but vastly better than memorizing 160-bit addresses. * José Founder, EatBCH Cash Accounts make addresses memorable by reducing the complexity to something like a discord account or a telephone number. * imaginary_username Enthusiast Quite a clever way to make account aliases both decentralized and immutable! * SpendBCH Bitcoin Cash Engineer, Badger Wallet Cash Account goes far beyond enhanced payments. It will finally bring about consistent identity, reputation, and discoverability to both end users and organizations. Cash Accounts Specification | Website Bug Tracker | Bitcoin Cash | Public Chat | Licensed with MIT