Search results

Jump to: navigation, search
  • ...each account refers to only one address or leaf node (obviously normal “accounts” will also exist). # Should allow referencing of accounts by offset and address.
    6 KB (1,052 words) - 13:11, 18 July 2014
  • ...omplete slices so that the node can be sure it has the all the [[Account | accounts]]. Finally, the node can use recent transactions to update all slices of th
    3 KB (510 words) - 08:32, 16 July 2014
  • ...antageous if we could prune this type of “dust” from the tree once the accounts were old enough. There are several ways this can potentially be achieved bu ...e made from the account we could have a system for allowing the pruning of accounts which would have a non-positive balance had they been paying their account
    2 KB (272 words) - 08:51, 16 July 2014
  • ...o [[Account | accounts]] in the account tree and the outputs also refer to accounts in the account tree. ...he balance of the input accounts to decrease and the balance of the output accounts to increase. Fees are still used as normal to give priority to transactions
    4 KB (600 words) - 13:14, 18 July 2014
  • ...sactions more secure. By allowing users to set a withdrawal limit on their accounts a merchant can see the balance and withdrawal limit of the buyers address a
    5 KB (858 words) - 03:45, 1 August 2014
  • ...using a special [[transactions|transaction]] and the default value for new accounts is unlimited. The purpose of such a system is to help prevent double spendi
    5 KB (910 words) - 19:05, 26 July 2014

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)