They updated the page with the link to the source adding a note saying the source code shown is old code but the new code will be added shortly.
That means they're still making changes. Merged mining could come back..? We'll have to wait and see.
|
|
|
32 bit? yes....
but the block chain which loads into memory on Windows boxes is over 2gigs so windows daemon won't run any more. Not sure if the 32-bit linux version has the same problem or not. I stopped running it recently.
|
|
|
40% of the p2pools haven't updated according to forrestv's post. Hopefully everyone here has updated. I PM'd everyone in the list but no one has responded if they have updated their software for the BIP16 transition. It would be nice if those running public nodes post in the thread that they've updated and I could add BIP16 to their connection information. Sorry, didn't know you were looking for a reply. My node was updated and ready before you sent that notice out. It is updated as of 2 nights ago.
|
|
|
40% of the p2pools haven't updated according to forrestv's post. Hopefully everyone here has updated.
|
|
|
I've been merge mining GG with my p2pool and have been getting blocks although the number has dropped significantly in the past day or two. Two connections and currently at block 1016444.
I sort of have a block explorer running for GG. It hasn't updated GG in a few days now since I had to move GG off to another box due high loads causing problems with p2pool mining.
Edit: I'm starting to think looking at the numbers that I've not received any credit in the last 24 hours as well. Updating my block explorer for GG to find out what's going on.
|
|
|
Yes, but you've been running for awhile. When you ran your p2pool node for the very first time how long did it take?
|
|
|
Your node has to be running for a while without the IP changing. It took me 12 hours (over night) before I saw my first connection. It was a few weeks later when I saw higher numbers.
|
|
|
Nope, nothing else you need to do.
I've done the same, forwarded port and waited. I've seen 30+ connections - 10 out and 20+ incoming to my node.
|
|
|
I was just about to open a request ticket on p2pool's git page for this.
|
|
|
Might be a bit more than just a change in the header hashing.. During the import I noticed every 2nd block reported "Ignored bit8 in version 0x00000100 of chain_id 22". Seemed a bit odd that every 2 blocks had a different header... Reading the MMMCoin forum today through google's translator it turns out that the block chain links blocks differently. - http://mmmcoin.org/forum/viewtopic.php?f=8&t=84&start=20#p447Every 2nd block put into the chain comes from the miners connected to the clients and the blocks in between are created by "trusted nodes". If someone solves a block and it gets put into the chain, no one else can solve another block until one of the trusted nodes puts a block in. miner block -> trusted node block -> miner block -> trusted node block ... etc. Seeing how every 2nd import by Abe reports ignoring bit8 I'd guess that there are 2 different block headers to process depending on the source of the block.
|
|
|
The import completed. SQL results: SELECT block_id FROM block WHERE block_hash LIKE '000003b4ef02c872071895b0308232%';
gave me empty results...
|
|
|
I've not noticed any extra hashes yet.
|
|
|
Current status: I had to enable the "ignore-bit8-chains" flag for MMMCoin. It failed with the same error I had with the bitcoin testnet. Import resumed. commit block_tx 1982463 5051769 commit Ignored bit8 in version 0x00000100 of chain_id 22 block_tx 1982464 5051770 block_tx 1982464 5051771 commit block_tx 1982465 5051772 block_tx 1982465 5051773 commit Ignored bit8 in version 0x00000100 of chain_id 22 block_tx 1982466 5051774 block_tx 1982466 5051775 commit block_tx 1982467 5051776 block_tx 1982467 5051777 commit Ignored bit8 in version 0x00000100 of chain_id 22 block_tx 1982468 5051778 block_tx 1982468 5051779 commit
|
|
|
Here's how a new import to a new db goes: :~/apps/bitcoin-abe$ python -m Abe.abe --config imports/abe-mmcoin-test.conf ddl_implicit_commit=true create_table_epilogue=' ENGINE=InnoDB' Abe/DataStore.py:418: Warning: Converting column 'a' from VARCHAR to TEXT store.cursor.execute(stmt) Abe/DataStore.py:418: Warning: Converting column 'b' from VARCHAR to TEXT store.cursor.execute(stmt) max_varchar=4294967295 clob_type=LONGTEXT binary_type=hex int_type=int Created silly table abe_dual sequence_type=mysql limit_style=native Assigned chain_id 8 to MMMCoin block_tx 1 1 commit block_tx 2 2 commit block_tx 3 3 commit block_tx 4 4 commit block_tx 5 5 commit block_tx 6 6 commit block_tx 7 7 commit block_tx 8 8 commit block_tx 9 9 commit block_tx 10 10
Config file: :~/apps/bitcoin-abe$ cat imports/abe-mmcoin-test.conf dbtype MySQLdb connect-args {"host":"removedserver","user":"removedusername","db":"abe-test","passwd":"removedpassword"} no-serve commit-bytes = 0
datadir = [{ "dirname":"/home/ed/.mmm", "chain":"MMMCoin", "code3":"MMM", "address_version":"\u0000"}]
And the same result when viewing through the web interface. http://i147.photobucket.com/albums/r300/lethaltiker/F4D42AF6A0326EB5EB858F2D4510FB78.jpg
|
|
|
I am curious about Abe's console output. Have you tried loading the currency to a fresh database with no other datadirs configured? I'm curious what Abe prints.
I haven't tried that yet but I can... I'll get a second import running to a new db while the existing one continues.
|
|
|
Not sure if this helps or matters but from reading the forums through Google's translator it seems like changes were made recently. The original client / network (if I read correctly) got hit with a 51% attack. A new client was released a few days ago with fixes for that. I don't know if it affects the block chain or not (beyond my knowledge of block chains). Also, if helpful, the client was compiled from sources pulled from https://github.com/alexhz/MMMCoin_public
|
|
|
The first occurance of the best= line (when I first launched the new client): Loading block index... Genesis block time: 1325369107 Genesis block bits: 1e0fffff Genesis block nonce: 386206 Genesis block hash: 00000f2e9f8ffa3abc79a4dcbff01dcfd10f480e897ebcd50cb0c37afbe57d51 Genesis merkle root: 7dee73b5c259a6e2eb06482b289af5cb7f24476310fc80081667baf8f2f27c5b SetBestChain: new best=00000f2e9f8ffa3abc79a4dcbff01dcfd10f480e897ebcd50cb0c37afbe57d51 height=0 work=1048577 block index 83ms
The last (or current) is: Flushed wallet.dat 24ms askfor block 000003b4ef02c872071895b03082326f807ee202bdfc33619c3b3122620c2188 0 sending getdata: block 000003b4ef02c872071895b03082326f807ee202bdfc33619c3b3122620c2188 askfor block 000003b4ef02c872071895b03082326f807ee202bdfc33619c3b3122620c2188 1331918649000000 received block 000003b4ef02c872071895b03082326f807ee202bdfc33619c3b3122620c2188 CalculateChainWork() : New trusted block at height 93363. Last work: 9233139665732, new work: 253336966, combined: 9233393002698 SetBestChain: new best=000003b4ef02c872071895b03082326f807ee202bdfc33619c3b3122620c2188 height=93363 work=9233393002698 ProcessBlock: ACCEPTED 03/16/12 17:24:12 Flushing wallet.dat Flushed wallet.dat 23ms
I don't understand the part about "and then bring abe up to date". I'm assuming it means import everything now so I'm going ahead with that now.
|
|
|
By runs fine I mean: block_tx 1919268 4979880 commit block_tx 1919269 4979881 commit block_tx 1919270 4979882 commit block_tx 1919271 4979883 commit
I didn't see any errors. First line was about new chain and setting new chain id. I hit CTRL C after about 100 blocks or so when I noticed the website wasn't updating properly. I'll see what I can find for the hash block and will reply. Give me a few. Thanks.
|
|
|
I have a new question / problem for you. I had to setup a new box to run alternate currencies because the existing box is getting too heavily loaded. New box setup with same OS, loaded on Abe and a new alternate currency MMMCoin Importing this new chain to the same MySQL db running on a 3rd box looks like it runs fine from the prompt but when looking at it from the web interface, it shows with 0 blocks. Clicking on block 0 shows a block but no links to the rest... Is this a problem with the the new chain or something with the new box I just setup? Abe site - http://blockexplorer.funkymonkey.org
|
|
|
|