|
1481
|
Bitcoin / Bitcoin Discussion / Re: Geopolitics and Crypto
|
on: February 04, 2016, 09:05:19 PM
|
|
I don't think anyone in front of any government would/will buy Bitcoin in the name of their government or country. Some may do it at a personal level and in an undisclosed way, though, why not?
I don't think governments buying into Bitcoin is a good idea... I hope they don't even touch it in any way.
|
|
|
|
|
1484
|
Bitcoin / Bitcoin Discussion / Re: Europe unfriendlyness is growing
|
on: February 02, 2016, 10:19:08 PM
|
|
Good that they're tracking "dirty" money and cutting resources to the terrorists... But good luck proving certain Bitcoin belong to terrorists and even better luck stopping those funds from getting transferred.
|
|
|
|
|
1488
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin 0.12 release
|
on: February 01, 2016, 06:24:52 PM
|
Guess I messed that section on the release notes. I went straight ahead to the pruning part to see if block relaying was enabled or not and it redirects to the release notes of v0.11.0, so I assumed that everything related to pruning was still pretty much the same as it is on 0.11. My bad  Regarding BIP 130, all clients 0.10+ support this? That's what I gather from reading it... No, only 0.12+ because the sendHeaders message does not exist prior to 0.12. Then we're back to square one, at least until pretty much everyone updates. Good thing about this it will probably make most people update |
|
|
|
|
1491
|
Bitcoin / Development & Technical Discussion / Re: Need shopping cart module that uses pre-generated address list
|
on: February 01, 2016, 06:01:15 PM
|
I wrote one a while ago in PHP, but haven't had the time to keep it up to date and secure.
It used a full node for blockchain information, accepted xpub's from admins/merchants/buyers, and generated multisig addresses. Private keys weren't stored or generated by the system, but eventually for usability, I allowed users to generate private keys using a passphrase in javascript. Convenience/Security trade off, but that's how it goes.
It lets users paste in signed raw transactions, or use the javascript thing to generate it in the browser if the user went that route. I'd love to revisit it, but it's a full featured site, not a module.
Any online websites with a demo of that? |
|
|
|
|
1495
|
Bitcoin / Bitcoin Technical Support / Re: Bitcoin full nodes with IPv4 and IPv6 - Why most peers are on IPv4?
|
on: January 31, 2016, 05:19:43 PM
|
I don't see any proof that your client is somehow not accepting IPv6 connections/preferring IPv4 connections or malfunctioning in any way. There aren't that many users with IPv6 on their connections (and I've definitely never had a node connected via IPv6, either on the different VPS services I used or in my home connection). The probability of having IPv4 nodes connected is pretty higher. Here are Google's IPv6 statistics. They're worth what they're worth... but it's a starting point to measure adoption. |
|
|
|
|
1496
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin 0.12 release
|
on: January 31, 2016, 05:05:20 PM
|
Guess I messed that section on the release notes. I went straight ahead to the pruning part to see if block relaying was enabled or not and it redirects to the release notes of v0.11.0, so I assumed that everything related to pruning was still pretty much the same as it is on 0.11. My bad Regarding BIP 130, all clients 0.10+ support this? That's what I gather from reading it... Additional constraints
As support for sendheaders is optional, software that implements this may also optionally impose additional constraints, such as only honoring sendheaders messages shortly after a connection is established.
Backward compatibility
Older clients remain fully compatible and interoperable after this change. Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.
Possibly a 2016 LTE phone could be capable of running 0.12 in pruned mode. Seems inevitable that will happen at some point, if not this year. That wouldn't be bad at all |
|
|
|
|
1498
|
Bitcoin / Development & Technical Discussion / Re: Bitcoin 0.12 release
|
on: January 31, 2016, 03:51:53 PM
|
|
It seems that block relaying is still disabled with pruned nodes, unfortunately. I'll be skipping these RC's. One thing at a time, I guess... Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.
|
|
|
|
|
1500
|
Bitcoin / Bitcoin Technical Support / Re: Raspberry Pi 2 Node
|
on: January 31, 2016, 03:14:44 PM
|
Is it possible to attach a screen to the Pi 2 and have it run information like the bitnodes hardware did? Their LCD code is here, how would one use this to have information being presented on screen? Yes, this is possible. Some specially designed screen are available on diverse website on the web. I think that they have to be connected to the 40-pin GPIO port, but I'm not sure at 100%. I know that there are screens and that they can be attached to the GPIO port, but my question is more software related: if I attach one of those screen how would I get on about making it work like it did on the bitnodes hardware? |
|
|
|
|
Show Posts
)
