Re: [Bitcoin-development] Code review
On Fri, Oct 04, 2013 at 02:14:19PM +0200, Mike Hearn wrote: One advantage of using github is that they're an independent third party; we should think carefully about the risks of furthering the impression that Bitcoin development is a closed process by moving the code review it to a server that we control with explicit review groups. I guess anyone would be able to sign up and comment. It's a long shot, but have any of you looked into Fossil? -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] moving the default display to mbtc
On Fri, Nov 15, 2013 at 01:37:56AM -0800, Alex Kravets wrote: Hi guys, Alex, you're top-posting and not trimming your replies. I've seen many many non-geeks be utterly intimidated and confused by 0.000X quantities and/or mBTC uBTC notation Yes, people really can't tell any difference between mm, cm, m, dm and km. Not. Yes, $10 being rougnly 10,000 Won in South Korean is a great example where large amounts of units work very well in a major economy. You're trying to invent a new symbol for the same unit, instead of using an established, generic system of prefixes. That's pretty insane. FWIW, I would prefer the entire switch-over be done *once* *and *at the same time switching both BTC to XBT and using the following I would prefer that nobody does any such silly thing. Currency Code *: *XBT Unit Definition *: *1 Bit = 100 Satoshis Addition benefit is splitting the term Bitcoin/bitcoin (as in Network and currency unit) into Bitcoin (network) and Bit (the unit). Bitcoin is not measured in bits. Bits are units of information, and are measured in bits, kbits, Mbits, Gbits, Tbits, Pbits etc. http://en.wikipedia.org/wiki/Bit_rate Perhaps this project/process should have a name and be listed on a road map somewhere What would a sane person think if he saw that on the roadmap, you think? *BRCS: *Bitcoin Re-denomination and [Currency] Code Standardization project Ever heard of SI unit prefixes? http://en.wikipedia.org/wiki/Metric_prefix Cheers ... On Fri, Nov 15, 2013 at 1:23 AM, Eugen Leitl eu...@leitl.org wrote: On Thu, Nov 14, 2013 at 05:53:16PM -0500, Alan Reiner wrote: I really like the XBT idea. It makes a lot of sense to match the ISO I really don't. Just use the SI prefixes. currency symbol (though the ISO guys will have to adjust the way they've defined the XBT). And I do agree that going right to uBTC and skipping mBTC makes sense, too. The display units should be choosable by the user. I'd prefer them not be called micro bitcoins. I really want to call them microbes ... but I'm not sure that has the right flavor for money Why on earth? transfer :) Please give me 872 microbes. Perhaps we just call them bits. Or even micros or microbits. As I write this, I realize there's probably 872 threads on the forums about this already... But we would want to promote a consistent term, to avoid further confusion when people use different names for the new unit. It's not guaranteed to be successful, but if we pick a good name, and build it into the interface on the first release pushing the new unit, we have a chance to make the transition even easier. The reason SI prefixes were invented is exactly to preven that case. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Alex Kravets http://www.linkedin.com/in/akravets def redPill = ' Scala http://www.scala-lang.org/ [[ brutal honesty http://goo.gl/vwydt is the best policy ]] -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[Bitcoin-development] please check my debug.log
I've put up some bitcoind nodes after the network is in need of some, and would like some feedback in that the nodes are fully operational and doing something useful. Please check the logs and tell me whether I'm doing good. debug.log from a node that has been running for a day: 2014-04-29 08:06:18 ERROR: CheckTransaction() : vin empty 2014-04-29 08:06:18 ERROR: AcceptToMemoryPool: : CheckTransaction failed 2014-04-29 08:06:18 Misbehaving: 122.224.182.248:23159 (0 - 10) 2014-04-29 08:07:00 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=298263, us=88.198.51.132:8333, them=0.0.0.0:0, peer=148.251.238.178:63657 2014-04-29 08:07:19 receive version message: /bitcoinseeder:0.01/: version 6, blocks=23, us=[2a01:4f8:131:13ed::2]:8333, them=0.0.0.0:0, peer=[2a02:348:5e:5a29::1]:53921 2014-04-29 08:09:37 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=88.198.51.132:8333, them=192.33.90.253:8333, peer=192.33.90.253:43104 2014-04-29 08:09:37 socket recv error 104 2014-04-29 08:10:26 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=298263, us=[2a01:4f8:131:13ed::2]:8333, them=0.0.0.0:0, peer=[2a01:4f8:202:81b1::2]:50624 2014-04-29 08:10:32 receive version message: /bitcoinseeder:0.01/: version 6, blocks=23, us=88.198.51.132:8333, them=0.0.0.0:0, peer=217.78.0.153:37275 2014-04-29 08:10:50 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=298263, us=88.198.51.132:8333, them=0.0.0.0:0, peer=148.251.238.178:50788 debug.log from a node that I just restarted: 2014-04-29 08:06:16 Opening LevelDB in /home/bitcoind/.bitcoin/blocks/index 2014-04-29 08:06:17 Opened LevelDB successfully 2014-04-29 08:06:17 Opening LevelDB in /home/bitcoind/.bitcoin/chainstate 2014-04-29 08:06:19 Opened LevelDB successfully 2014-04-29 08:06:22 LoadBlockIndexDB(): last block file = 135 2014-04-29 08:06:22 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=631, size=128154379, heights=297633...298263, time=2014-04-25...2014-04-29) 2014-04-29 08:06:22 LoadBlockIndexDB(): transaction index disabled 2014-04-29 08:06:22 LoadBlockIndexDB(): hashBestChain=162f5f571eef4742b70204d983bda3c4b18fc1496ac27f86 height=298263 date=2014-04-29 08:00:23 progress=0.81 2014-04-29 08:06:22 init message: Verifying blocks... 2014-04-29 08:06:22 Verifying last 288 blocks at level 3 2014-04-29 08:07:42 No coin database inconsistencies in last 289 blocks (89 transactions) 2014-04-29 08:07:42 block index 86284ms 2014-04-29 08:07:42 init message: Loading wallet... 2014-04-29 08:07:42 nFileVersion = 90100 2014-04-29 08:07:42 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total 2014-04-29 08:07:43 wallet 108ms 2014-04-29 08:07:43 init message: Rescanning... 2014-04-29 08:07:43 Rescanning last 39 blocks (from block 298224)... 2014-04-29 08:07:43 rescan 204ms 2014-04-29 08:07:43 init message: Loading addresses... 2014-04-29 08:07:43 Loaded 14015 addresses from peers.dat 84ms 2014-04-29 08:07:43 mapBlockIndex.size() = 298264 2014-04-29 08:07:43 nBestHeight = 298263 2014-04-29 08:07:43 setKeyPool.size() = 100 2014-04-29 08:07:43 mapWallet.size() = 0 2014-04-29 08:07:43 mapAddressBook.size() = 1 2014-04-29 08:07:43 AddLocal(213.239.218.20:8333,1) 2014-04-29 08:07:43 IPv4 eth0: 213.239.218.20 2014-04-29 08:07:43 AddLocal([2a01:4f8:a0:74c8::2]:8333,1) 2014-04-29 08:07:43 IPv6 eth0: 2a01:4f8:a0:74c8::2 2014-04-29 08:07:43 ext-ip thread start 2014-04-29 08:07:43 dnsseed thread start 2014-04-29 08:07:43 Loading addresses from DNS seeds (could take a while) 2014-04-29 08:07:43 net thread start 2014-04-29 08:07:43 upnp thread start 2014-04-29 08:07:43 opencon thread start 2014-04-29 08:07:43 addcon thread start 2014-04-29 08:07:43 dumpaddr thread start 2014-04-29 08:07:43 msghand thread start 2014-04-29 08:07:43 init message: Done loading 2014-04-29 08:07:43 GetMyExternalIP() received [213.239.218.20] 213.239.218.20:0 2014-04-29 08:07:43 GetMyExternalIP() returned 213.239.218.20 2014-04-29 08:07:43 AddLocal(213.239.218.20:8333,4) 2014-04-29 08:07:43 ext-ip thread exit 2014-04-29 08:07:44 receive version message: /Satoshi:0.8.6/: version 70001, blocks=298263, us=213.239.218.20:44169, them=166.78.243.104:8333, peer=166.78.243.104:8333 2014-04-29 08:07:44 Added time data, samples 2, offset +8 (+0 minutes) 2014-04-29 08:07:51 No valid UPnP IGDs found 2014-04-29 08:07:51 upnp thread exit 2014-04-29 08:07:53 connect() to 71.23.29.162:8333 failed after select(): No route to host 2014-04-29 08:07:53 receive version message: /Satoshi:0.9.1/: version 70002, blocks=298263, us=213.239.218.20:46921, them=91.238.134.58:8333, peer=91.238.134.58:8333 2014-04-29 08:07:53 Added time data, samples 3, offset +0 (+0 minutes) 2014-04-29 08:07:54 106 addresses found from DNS seeds 2014-04-29 08:07:54 dnsseed thread exit 2014-04-29 08:08:16 receive version message: /Satoshi:0.8.6/:
Re: [Bitcoin-development] Why are we bleeding nodes?
On Tue, May 20, 2014 at 10:15:44AM +0200, bitcoingr...@gmx.com wrote: Recently China has updated its firewall blocking bitcoin sites and pools. Whether this is simple blacklist or more sophisticated packet targeting is uncertain, however this update did spefically target VPN handshakes. Could a blockchain fork due to network split happen? -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
