Near-term scalability

One topic of debate was the use of fee algorithms, with a consensus that using the same algorithms as Bitcoin-Qt would prevent excessive fees and queue-jumping. The issue of address reuse was also discussed, with some concerns raised about complicating certain use cases and increasing the address index used by block explorers and lightweight client servers.In terms of scalability improvements, there was agreement that making the block size limit float would be more beneficial than setting an arbitrary threshold. However, concerns were raised about the potential centralization that could result from implementing blockchain pruning. Some participants argued that technical solutions could address this concern without changing trust requirements.To address concerns about large blocks slowing down end user syncing and wasting resources, it was suggested that Simplified Payment Verification (SPV) clients like MultiBit and Android Wallet could help. Additionally, implementing bloom filtering P2P commands could reduce excessive bandwidth usage and parse overheads for end-users.In a discussion specifically about scalability and SatoshiDice, the participants agreed that it would be desirable for senders/buyers to pay no fees. However, they acknowledged that this may eventually be necessary. Proposals were made to deprioritize rapidly-reused addresses by limiting the count of address reuses in the memory pool. Various other proposals were discussed, including grouping transactions together with their mempool dependencies and using the same fee algorithms as Bitcoin-Qt for SatoshiDice.Overall, the discussions focused on finding practical solutions to improve the functionality and accessibility of Bitcoin while also considering the potential consequences and trade-offs. The goal was to encourage widespread adoption and competition among currencies while maintaining decentralization and low costs for operating a fully validating node.