(live set, archival set), non-lightning payment channelsġ2:02 nonmining block signing is technically a scalability proposal (private chain signing stuff)ġ2:15 utxo set + zero-knowledge proof / snark of the entire blockchain history (asymptotically less verification time, unknown size, proof would take forever to create), merklerize the entire blockchain or do the same thing as the compact spv proofs- embed the header. read all satoshi nakamoto posts to bitcointalkġ2:00 treechains, sidechains, bloomtables, libsecp256k1, bdb -> leveldb, block database is maybe leveldb now, utxo scaling with p2sh to make multisig smaller, schnorr signature stuff, tree signatures, not ring signature stuff because it makes scalability worse, borromean ring signature stuff for confidential transactions, spv itself is scalability related, lightning network, atomic cross-chain swap stuff, centralized proposals and off-chain stuff, look at gmaxwell's hardfork wish list, look at gmaxwell's altcoin wishlist, merkelized abstract syntax trees (script executing happens in the merkle tree, satisfying a script only needs to reveal the merkle branch (both scalability and privacy)) ((tree sigs are a special case), drop the OP_RETURN data proposals, drop old utxos (petertodd has a thing about recovering old dropped utxos with some proofs) (you keep your own utxos) bitcointalk deep dive of technical subforum: only 185 pages of threads, get thread list in a single. bitcointalk shallow dive: all threads started by above list of people You, sipa, petertodd, adam3us, maaku, socrates1024, killerstorm, tiernolan, jgarzik, etotheip, jl2012, gavinandresen, mike hearn, satoshi nakamoto (none? wtf), wumpus, jtimon, nanotube, bytecoin what's the performance of libsecp256k1? how many bitcoin transactions per second can be signed by libsecp256k1? openssl? etc. how many bitcoin transactions per second can be created outside of the network? This gives an appropriate time and place for the user to set their proxy settings, define their own node(s) for bootstrapping, select WAN or LAN operation and other future settings that are included.Bryan's list of max block size proposals that was sent to the bitcoin-dev mailing list Then the user could make their changes and restart bitmessage at which point everything would happen the way they want it to. If a user wishes to use bitmessage with a proxy (including Tor) then they would have to disable their internet connection before starting bitmessage, make the changes, stop bitmessage, enable their internet connection, then start bitmessage.Ī notification window stating "This is the first time running Bitmessage, would you like to: Connect using the default settings, Connect using custom settingsĭepending on which choice is selected, the appropriate action would occur.Ĭhosing "Connect using custom settings" could do nothing more than prevent bitmessage from connecting to the network. When a user is first starting bitmessage (no keys.dat file) their client immediately connects to the network using the default settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |