Same shit, different name I'd say..
So far i had the impression that the world has taken the arabic (indian..) numbers as standard and those in a decimal system. Who actually uses Tonal or Radial numbers? And for what?
*edit* been reading a bit into the tonal system and i got to say: "WHY??" its just a hexadecimal system with funny letters.. except for some poeple trying to reinvent the clock and the calendar i dont see any real reason for its existance.. am i missing something?
Topic: Please test (if you dare): next-test 20120321 (Read 2376 times)
....why Tonal?!
Isnt there something even more overfluent you might have used instead?
Tonal is the whole reason I'm involved with Bitcoin. "Overfluent" doesn't seem to be in any dictionary, so I don't know what it means.Isnt there something even more overfluent you might have used instead?
Sorry, no native spaker here, thought that translation would exist. I will rephrase the question:
"Isnt there something even more useless you might have used instead?"
....why Tonal?!
Isnt there something even more overfluent you might have used instead?
Tonal is the whole reason I'm involved with Bitcoin. "Overfluent" doesn't seem to be in any dictionary, so I don't know what it means.Isnt there something even more overfluent you might have used instead?
Sorry, no native spaker here, thought that translation would exist. I will rephrase the question:
"Isnt there something even more useless you might have used instead?"
blockchain.info did before the the mystery miner changed tactic and either started relaying only to mining pools or blocked my nodes.
I suspect he blocked your nodes. The IP in question does have port 8333 open.I'm guessing 88.6.208.35 or an ip in a similar subnet?
Same /16 subnet. 
Quote
It's a Spanish IP, but not one blockchain.info seems to know anything about.
blockchain.info did before the the mystery miner changed tactic and either started relaying only to mining pools or blocked my nodes. I'm guessing 88.6.208.35 or an ip in a similar subnet?
[This handy-but-simple change enabled me to get the real IP of the actual server making these blocks.
You dont know that. You get the IP of whomever is relaying the block. How do you know it actually made it?
Is it the spanish Telefonica one?
It's a Spanish IP, but not one blockchain.info seems to know anything about.....why Tonal?!
Isnt there something even more overfluent you might have used instead?
Tonal is the whole reason I'm involved with Bitcoin. "Overfluent" doesn't seem to be in any dictionary, so I don't know what it means. Isnt there something even more overfluent you might have used instead?
This handy-but-simple change enabled me to get the real IP of the actual server making these blocks.
Is it the spanish Telefonica one?
[This handy-but-simple change enabled me to get the real IP of the actual server making these blocks.
You dont know that. You get the IP of whomever is relaying the block. How do you know it actually made it?
....why Tonal?!
Isnt there something even more overfluent you might have used instead?
Isnt there something even more overfluent you might have used instead?
By default if you can steal the log of someone, you then can steal there wallet.dat. (that may or may-not be usefull, if the wallet is encrypted or not)
Right, the concern was that someone might attack (perhaps legally; ie, a visit from the police) for the logs themselves if they all contained this information. If someone could get logs full of IPs from lots of people, it could enable some more serious privacy invasions. 
By default if you can steal the log of someone, you then can steal there wallet.dat. (that may or may-not be usefull, if the wallet is encrypted or not)
I apologize for my outburst. I now understand.
I cede the remainder of my time to future statements.
I cede the remainder of my time to future statements.
Whenever a block is received, log the sender's IP and the current time
Go fuck yourself, Luke. I know you proposed this crud.
Actually, it was proposed by a pool member who noticed the mystery jerk miner was relaying his poisonous blocks through Eligius. I implemented it. This handy-but-simple change enabled me to get the real IP of the actual server making these blocks. No idea why you have a problem with logging useful information. The only objections have been on the basis of someone potentially stealing logs for the info. Go fuck yourself, Luke. I know you proposed this crud.
Whenever a block is received, log the sender's IP and the current time
Go fuck yourself, Luke.
Seems that is still under debate.Go fuck yourself, Luke.
Lulz...sounds like more people will learn how to compile.
Whenever a block is received, log the sender's IP and the current time
Go fuck yourself, Luke. I know you proposed this crud.
Go fuck yourself, Luke. I know you proposed this crud.
next-test is a branch of the mainline bitcoind & Bitcoin-Qt with as many pull requests merged as possible, to aid in testing them. This branch can be used to test many pull requests in your daily Bitcoin use. The goal is to help pull requests get the testing they need to be merged into the main tree, so once you test a change, please comment in the relevant pull request (ideally with details).
Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLET
Today's next-test includes the following pull requests (green are merged now; red are disputed):
Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLET
Today's next-test includes the following pull requests (green are merged now; red are disputed):
- Typo-tolerant (optimized) Base58 parser
- Parse URIs with non-BTC amounts
- -acceptnonstdtxn option to skip "non-standard transaction" checks
- Optimized binary-to-hex converter (ToHex)
- FastGetWork optimization
- Multithreaded JSON-RPC with HTTP 1.1 Keep-Alive support
- Specify fees explicitly via JSON-RPC
- Coinbaser
- Support for multiple local addresses
- Added 'immature balance' for miners. Only displayed if the balance is > 0
- gettransactions() for non-wallet transactions
- Toggle hide
- Add -loadblock to load from an external blk000?.dat file
- More details for getblock and gettransaction
- JSON-RPC call to accept transactions that don't meet acceptance fees
- Don't create change when it isn't necessary.
- Refactor SelectCoinsMinConf() and add unit tests.
- Add a menu option and dialog to verify a signed message
- Reopen log file on SIGHUP
- Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)
- Add a pong message that is sent in reply to a ping.
- Bugfix: BIP22: getmemorypool
- Move QMAKE_LIBS_QT_ENTRY adjustment to bitcoin side of build
- When disconnecting a node, the receive buffer should be cleared
- Prevent stuck block download in large reorganisations
- VC2010 compile fixes
- Limit getheaders to a hard 2000.
- language updates for source file bitcoin_en.ts + remove cs_CZ (issue #958)
- Speed up block downloading
- The generic UNIX Makefile builds with lots of warnings
- Whenever a block is received, log the sender's IP and the current time
Jump to: