To enhance ease-of-use with LTB Companion and Token Pockets wallet, please integrate the following scheme when displaying addresses so users may more easily send tokens to each other and avoid sending tokens to addresses that do not know how to see or deal with them.
Places where click-to-pay addresses should show up
As a button beside the fully visible address on each User Profile page
As a button beside the fully visible address on each Individual Content Page
As a button with only the first few characters of the address displayed to fit in the confined space while still letting users quickly double check that the address is correct. The primary small-space is User Information in the sidebar when posting in forums
To do this we'll need to give users the ability to define what tokens they'll accept account-wide with the ability to add or remove specific tokens from specific addresses.
it makes sense to turn the "Bitcoin Tip Address" field into a dropdown menu that lets the user select one of the addresses associated with their account (whether verified or not) - This gives us the information about whether or not the address is counterparty compatible. By default addresses verified as counterparty should accept ALL tokens and all counterparty compatible addresses should accept LTBCOIN even if all other tokens besides BTC are turned off. Within the LTB platform ecosystem, everyone needs to at least be willing to be given LTBCOIN even if they immediately sell it for something they value more, and of course the merchant always defines the premium they demand for accepting the token.
Implementation Examples
Example that would accept all tokens
<span class="companion-tip-button" data-address="1Dhx3kGVkLaVFDYacZARheNzAWhYPTxHLq" data-label="All the tokens" data-tokens="all"></span>
Example that would accept BTC or any other single token only
<span class="companion-tip-button" data-address="1Dhx3kGVkLaVFDYacZARheNzAWhYPTxHLq" data-label="bitcoin only" data-tokens="btc"></span>
Example that would accept only user-defined tokens
<span class="companion-tip-button" data-address="1Dhx3kGVkLaVFDYacZARheNzAWhYPTxHLq" data-label="specific tokens" data-tokens="ltbcoin,fldc,sjcx"></span>
**Note: use all or no capitalization when describing date-tokens, LTBCOIN,FLDC,SJCX or ltbcoin,fldc,sjcx - mixed capitalization will not work.
To enhance ease-of-use with LTB Companion and Token Pockets wallet, please integrate the following scheme when displaying addresses so users may more easily send tokens to each other and avoid sending tokens to addresses that do not know how to see or deal with them.
Places where click-to-pay addresses should show up
To do this we'll need to give users the ability to define what tokens they'll accept account-wide with the ability to add or remove specific tokens from specific addresses.
it makes sense to turn the "Bitcoin Tip Address" field into a dropdown menu that lets the user select one of the addresses associated with their account (whether verified or not) - This gives us the information about whether or not the address is counterparty compatible. By default addresses verified as counterparty should accept ALL tokens and all counterparty compatible addresses should accept LTBCOIN even if all other tokens besides BTC are turned off. Within the LTB platform ecosystem, everyone needs to at least be willing to be given LTBCOIN even if they immediately sell it for something they value more, and of course the merchant always defines the premium they demand for accepting the token.
Implementation Examples
Example that would accept all tokens
<span class="companion-tip-button" data-address="1Dhx3kGVkLaVFDYacZARheNzAWhYPTxHLq" data-label="All the tokens" data-tokens="all"></span>Example that would accept BTC or any other single token only
<span class="companion-tip-button" data-address="1Dhx3kGVkLaVFDYacZARheNzAWhYPTxHLq" data-label="bitcoin only" data-tokens="btc"></span>Example that would accept only user-defined tokens
<span class="companion-tip-button" data-address="1Dhx3kGVkLaVFDYacZARheNzAWhYPTxHLq" data-label="specific tokens" data-tokens="ltbcoin,fldc,sjcx"></span>**Note: use all or no capitalization when describing date-tokens, LTBCOIN,FLDC,SJCX or ltbcoin,fldc,sjcx - mixed capitalization will not work.