Why would it be replaced instead of just updated/extended/patched?
So what has replaced the internet (TCP and IP protocols)? They have a ton of flaws & shortcomings. There are lots of things which could be done better if you replaced everything from the ground up with a new set of protocols. The internet looks nothing like the internet of the early 1980s but the low level protocols are still there. They have been extended and upgraded but not replaced with a brand new system.
Did I miss the memo where we just ripped up the entire internet and replaced it with something new?
FYI, in case you haven't noticed: people are beginning to use ipv6 now. |
|
|
|
How much should I pay for you?
12UybofC48388JwaSptJZMy6YAudTZFVZH - 40 btc. |
|
|
|
Short term alert to subscribers issued.
that cannot be very bullish. yes there is. you would not have wrote "ALERT!!!" if it was neutral. so now we have only bullish or bearish to choose between. |
|
|
|
Short term alert to subscribers issued.
that cannot be very bullish. i think you are wrong. i think the alert is like "if the price goes above X it will go way above X" not "DOWN DOWN DOWN!". |
|
|
|
Thanks guys  you're awesome! |
|
|
|
Good luck with that. (thats why i don't code in C,  ) |
|
|
|
Great another academic wasting tax payers money on fancy long words.
if the did not waste tax money, we would not have computeres. |
|
|
|
|
the goal of bitcoin is not and has never been to bring freedom to money, be anarchistic, or in anyway be a revolutionary force against the establishment. it is on the other hand these ideas the fostered bitcoin in the first place.
the goal of bitcoin is to explore how currencies can function in a system of equal peers, and how to solve problems no one have solved before. in bitcoin's case this goal is accomplished by a blockchain which timestamp transactions in batches, and is based on that on computationally hard to make a fake block. it could be accomplished by some other means like proof of stake(which again is a blockchain layout), or by some awesome-math-stuff that have yet to be discovered.
the goal of bitcoin is therefor not a political one, but a technological one.
(btw. if the governement asked me to pay taxes on bitcoins i have earned i would happily pay them. but as it stands now, i have no idea how to do so, so i don't...)
|
|
|
|
|
signal(SIGPIPE, SIG_IGN) ?
|
|
|
|
I think there should be some special notes added to the API documentation (or at least a link to something) to describe clearly what Bitcoin "accounts" actually are because much of the negative views about them is due to not understanding them correctly (such as thinking they are the same as "coin control").
THEY CAN HAVE NEGATIVE BALANCES!!! feature? bug? |
|
|
|
|
it is missing a "they suck!!! kill them before they lay eggs!!" vote.
|
|
|
|
Nice! im only testing against the satoshi client for now. im also making an alternative client in python. so far i can download and verify blocks and transactions(mostly... have implemented a hacky replacement for the scripting, just ripping out the sig and publickey and checks if it verifyes...). i have no working wallet for now, but i can send hand crafted transactions. If you are using python, please consider using the 'bitcoin' module found in https://github.com/jgarzik/pynodeIt already does full script and block verification. The only major to-do is chain reorg, and that does not impact the 'bitcoin' module at all. +1 will look into it.  |
|
|
|
Good luck with that python project. I take it that the client will use the SPV model?
no, it will be a full blown client. but it will be very modular so a SPV would be very simple to make with the codebase cbitcoin wont be a bitcoin client but will provide the low-level interface for creating a client. After cbitcoin reaches alpha stage I will start working on the client on top of cbitcoin which is currently code-named BitEagle. awesome! And I'm close to alpha stage. I've just got to sort out the address discovery and do the block validation code. cbitcoin wont relay/download transactions or blocks. cbitcoin only has a low level interface to the bitcoin network and also provides handshakes, pings and address discovery. You can choose to turn these features on or off using flags, so for instane you may not want address discovery if you plan to connect to specific nodes only and you may wish to implement your own behaviour. i python i have created a seperat class, that controls block down/up-loading behavior, and another class that keeps track of the addresses. ...and i have not implemented ping yet, because im lazy and its not really an important feature(but connections closes sometimes...) happy coding! |
|
|
|
|
okay... you do know that people don't care, right?
(sorry for being rude)
|
|
|
|
|
the output from curl_exec is already in json, you are double encoding with json_encode, hence the \"
|
|
|
|
Thanks for the suggestions. I don't really know what caused it but I did see an issue with attempts to allocate zero memory. I fixed all that by using NULL to represent nothing as I was intending to. After fixing all that and some other issues the problem went away. Now the handshake works and I've committed an update to github. EDIT: what clients are you testing with? both cbitcoin, or is one of them the satoshi client? which one then?
At the moment just cbitcoin but I will try connecting to the satoshi client as well. Edit: Pings work fine. Moving onto address discovery. Nice! im only testing against the satoshi client for now. im also making an alternative client in python. so far i can download and verify blocks and transactions(mostly... have implemented a hacky replacement for the scripting, just ripping out the sig and publickey and checks if it verifyes...). i have no working wallet for now, but i can send hand crafted transactions. |
|
|
|
Hmm. Now I'm getting an unexpected connection closure via 0 returned from read(). I printed out some of the data to try and understand what was happening:
Connection initiated by A
Connection accepted by B
Connection OK
A sent version header
A sent version payload
B received version header
B received version payload
B sent verack
B sent version header
B send version payload
A received verack
Connection closed
This is pretty odd, I don't know where to start looking... The thing is, neither A or B close the connection explicitly, they both receive 0 from read().
A does not receive the version from B? my guess: its A that closes the connection. can you post the version packets+headers? EDIT: what clients are you testing with? both cbitcoin, or is one of them the satoshi client? which one then? |
|
|
|
|
you seems to have a limited understading of bitcoin. you does not need multiple bitcoind, unless you have very very special needs. which i doubt you have.
also it is not clear what it is you are trying to accomplish, please specify... (visual aids is not specifying, its just dumb and annoying, unless its very relevant and meaning full)
|
|
|
|
|
i don't know about OSX. but linux's man page for connect(2). does not say that connect can return ENOENT.
what kind of socket do you make, ipv6 or ipv4? not for the connect() call, but for the socket() call.
|
|
|
|
|
you are wrong!
this is a kangaroo court!
you are guity to proven otherwise.
this it not some highly ethical lawyer shit.
this is angry people who think you have stolen their money.
this is the gun-or-bat people, who does not trust in the any legal system, calling themselves anarchists.
these anarchistic people, will hurt you, if you don't give them their money back.
bitcoin gained popularity not among lawyers, politicians, and highly moral people.
bitcoin gained popularity among people with guns, people who does not respect the law, drugdealers, and other people who can hurt you.
|
|
|
|
|
Show Posts
