I wonder how much time will I need to study the Satoshi's client..  A lot! But a lot less, if you ask questions!  |
|
|
|
|
Have you tested block chain reorg? i.e. where a previous-best chain is overtaken by a stronger chain, causing transactions to be un-confirmed?
|
|
|
|
Just curious - did the JSON commands change between version 0.3 and 0.7? I tried using sendmany with the same code I used on 0.3, but it doesn't work in 0.7. I haven't rolled back to 0.3 to try it again (is there a legitimate place to download 0.3 from still?), but I haven't changed any of the code since the last time I used it on 0.3 either.
" Warning: fopen(http://...@127.0.0.1:8332/) [function.fopen]: failed to open stream: HTTP request failed! HTTP/1.1 500 Internal Server Error in C:\wamp\www\includes\jsonRPCClient.php on line 132"
'sendmany' should be unchanged, AFAIK. Want to post a debug.log snippet? |
|
|
|
As for Mircea Popescu's accusations, they are largely baseless.
[...]
So it's just FUD.
Unsurprising, as MPOE-PR is a competitor |
|
|
|
P.S. While not bitcoin-related, for the Unix geeks in the audience, here are my plates: http://yyz.us/box.html |
|
|
|
My plates have the first bits for one of my addresses. Ok, that was a lie. They're actually just a random DMV-selected alphanumeric string, but there's no harm in pretending, is there?
heh, with the proper application of CPU/GPU power, it is actually possible to turn that lie into truth. See vanitygen. |
|
|
|
|
Good stuff. Keep up the good work!
I think there are USB simulators to be found, which would make testing this easier.
|
|
|
|
|
Here in Raleigh, North Carolina, I saw someone in a car in front of me with "BITCOIN" on their license plate.
Almost broke into a ridiculous frenzy of honking and waving... what are the odds, that someone with a "BITCOIN" plate would be at a stoplight right in front of a bitcoin core developer?
|
|
|
|
Amazon is heavily entrenched in and dependent on the traditional financial system, and its providers probably have an interest in compelling a company like Amazon from getting involved with bitcoin.
Sadly quite true. Amazon (as Amazon Payments) spend tons of money and lawyer time registering themselves with each and every US state as a money transmitter, MSB or similar. It seems likely that Amazon would jump on the bitcoin bandwagon after it hits major adoption. |
|
|
|
The service they provide by bouncing transactions for free between listening nodes can be gained just by having the initial broadcaster make more outbound connections.
...then logically, with most users running with standard defaults, there is benefit. As stated. |
|
|
|
How about instead of ad hominem attacks you actually read through his 9000 lines of code already written and find something concrete to criticize? Wouldn't that be more relevant and productive than questioning his capability based on a brief observation? And why not encourage him to try and fail if nothing else, it's not like his failure will be forced upon anyone else but his success might be good for a lot of people, no?
It's not a brief observation. We've been on IRC, teaching him the bitcoin basics for (months?) now. It is good to have people learning bitcoin, and putting that knowledge to use. It is not as good when obviously-still-learning people are billing their project as the "future of bitcoin" and misleading people into thinking they are a bitcoin expert, and are misleading people into thinking they are producing high quality, proven code (and potentially taking thousands of dollars for it). Those who are not coders lack the skills to judge this sort of thing, and only have hype from this thread to go on. |
|
|
|
Yes and ShadowOfHarbringer was most likely speaking of the 120 confirmation requirement. The answer to the original question is therefore that cbitcoin will not have this 120 confirmation restriction since cbitcoin will not restrict what transactions you can produce and broadcast. You can use it to create any transactions you want. It doesn't mean all transactions will be accepted by the network and cbitcoin will include checks on received relayed transactions.
You have just admitted that you are creating a non-compliant codebase, which will create invalid transactions. In that case, maybe people should redirect their donations and attention elsewhere. Other bitcoin clients include this requirement because it is.... a requirement. |
|
|
|
If a full node is behind a firewall (that you have no control over) and thus cannot accept incoming connections, is it still useful to the network? Or is it just taking up incoming ports on other nodes that would be better if left available for other clients?
Yes, it is useful. Every full node, even behind a firewall, is a node that helps ensure the block chain and transactions are valid. Each full node is a "vote" for the proper block chain. |
|
|
|
EDIT:
By "fresh" coins i mean just received coins but having 6-7 confirmations. Official client won't allow to re send these, so this is the reason i created my fork.
So the satsohi client doesn't allow you to make transactions from outputs just found, even when they have 6 confirmations??? Of course it does. You may make transactions from any output with at least one confirmation... except for newly generated blocks, as another poster noted. Generated blocks are not considered "mature" and spendable until 120 confirmations. |
|
|
|
There is already a blockchain torrent. See this: https://bitcointalk.org/index.php?topic=117982.0Additionally, if you are getting a slow network sync inside the bitcoin client, simply stop and restart. This will get you a new download peer. |
|
|
|
This is not a client, it is a library. And I'm replacing the GPLv3 with either a dual license or the GPLv3 with exceptions whichever turns out to best. I want to remove some of the nasty bits of GPLv3 as I admit that there are nasty bits.
If you look at the links provided, you will see libraries used by said clients. |
|
|
|
Isn't the only standard multi-sig implementation the P2SH one?
Multi-sig and P2SH are two totally different things. P2SH requires a script -- any script, containing CHECKMULTISIG or not -- to redeem. Multi-sig scripts may appear in non-P2SH transactions. P2SH is a layer on top of scripts, essentially. |
|
|
|
If this was just another client, great! We like alt implementations. The more clients, the healthier the ecosystem. But marketing this as "the route to bitcoin's future" is a bit much. There are already several other node implementations out there, including C implementations: ufasoft-coin, bitsofproof, and pynode. Not to mention SPV clients like BitcoinJ, Electrum and picocoin. The licenses are more liberal than GPLv3 as well. |
|
|
|
Do you think it is feasible for me to maintain a separate powerpc fork. As I understand all the modifications for ppc should relate to functions which do byte-ordering related stuff. Since you know the source probably better than I, is there a lot of byte-fiddling in bitcoin?
I doubt there would be need for a fork. As soon as someone, anyone, makes the effort to audit the source code and fix all the endian issues, we would likely just merge that patch into mainline bitcoin. |
|
|
|
|
Show Posts
