Topic: (Experimental) pident — a pool-biased blockchain representation (Read 5460 times)
Great, work, thanks!
October 31, 2011, 10:25:56 AM
The first 120k blocks are on sourceforge, zipped and ready to download
October 31, 2011, 03:28:27 AM
psy: In what experience I had, the biggest barrier is doing the initial load of the blockchain. It was fairly I/O intensive and wrought havoc with my VPS. I eventually had to give up (as it would have taken several days to finish), and run it instead on my local machine. However, the particular host machine my VPS is on has had a history of high I/O load from other users, so it's possible it might work better elsewhere.
Yeah, it took several hours for me too, the first time. It was really frustrating actually when debugging it, when the integrity breaks near the end and you have to restart everything just to debug it!
But, if you can manage to get a somewhat recent dump of the db, inserting the new missing blocks is faster. The latest backup I have is from late august and is about 420M.
October 30, 2011, 07:01:23 PM
I've been running my local bitcoind with the getblockbycount patch just fine. The patch has to be somewhat manually applied because there are conflicts since the last time that branch was rebased or merged. Someone should either update that branch or put an updated version somewhere else. Or even better, get the patch merged into bitcoin.
psy: In what experience I had, the biggest barrier is doing the initial load of the blockchain. It was fairly I/O intensive and wrought havoc with my VPS. I eventually had to give up (as it would have taken several days to finish), and run it instead on my local machine. However, the particular host machine my VPS is on has had a history of high I/O load from other users, so it's possible it might work better elsewhere.
psy: In what experience I had, the biggest barrier is doing the initial load of the blockchain. It was fairly I/O intensive and wrought havoc with my VPS. I eventually had to give up (as it would have taken several days to finish), and run it instead on my local machine. However, the particular host machine my VPS is on has had a history of high I/O load from other users, so it's possible it might work better elsewhere.
October 30, 2011, 09:01:37 AM
I wouldn't mind hosting it. Have an empty VPS I could use for it. But fixing it is out of my capacity as I'm not a programmer ;P
What would be the minimum requirements for the server?
What would be the minimum requirements for the server?
October 30, 2011, 08:15:12 AM
Didn't see this till today... do you still want that fixed patch, or have you abandoned pident entirely in the meantime?
Well, I don't think I will run a pident instance here on the foreseeable future, although it would be nice to actually have it in a runnable state, if anyone else wants to host it
October 30, 2011, 08:10:42 AM
Didn't see this till today... do you still want that fixed patch, or have you abandoned pident entirely in the meantime?
October 03, 2011, 02:41:49 PM
so it is down for good?
Until someone can manage to get a working bitcoind with the getblockbycount patch, pretty much. Good news is, you can still toy with it, the source is still out there!
October 03, 2011, 01:32:41 PM
so it is down for good?
October 03, 2011, 01:15:24 PM
Ok who broke the server!
Turns out I did. The patched "getblockbycount" branch does not compile with the newer miniupnpc versions, so I'm basically stuck here. If anyone can fix it, it's cool. Since I didn't get any feedback about pident in the last few weeks, I thought nobody was really using it anyway…
(And, of course, merging the old getblockbyhash branch in the new tree fails. And I'm not that great with C++.)
October 01, 2011, 05:03:14 PM
Ok who broke the server!
October 01, 2011, 04:05:37 PM
Seems stuck. It is not showing any updates since:
12 hours and 13 minutes ago 147,603 00000000000001b77b706b389df3ddfa9f161b66402092abc941e4dcd3f61cbc 4532 bytes DeepBit Scores
12 hours and 13 minutes ago 147,603 00000000000001b77b706b389df3ddfa9f161b66402092abc941e4dcd3f61cbc 4532 bytes DeepBit Scores
September 09, 2011, 09:43:36 AM
Hello everyone. Sorry, I moved out and I only got my internet connection back right now… I'm still quite content to see it worked fine except for the "pools not showing" problem.
It should be fixed now. Email me or reply if you have more issues
It should be fixed now. Email me or reply if you have more issues
September 08, 2011, 07:59:48 PM
Completely down now???
Each block is still being scored, just no verified owners... September 08, 2011, 07:02:53 PM
Completely down now???
September 07, 2011, 05:59:55 PM
Only three confirmed block owners since block #144,352, and none since #144,364. Did something radical change in the last 8 hours?
September 02, 2011, 08:27:39 AM
Okay, the recent changes are enough for a version bump (because why not?). There is now a cool SVG graph of pool sizes, pools are now correctly sorted by descending size. Added support for BTCServ and readded RFCPool (yes, they repoened!).
I'd like to add BitClockers, ABCPool and NinjaCoin to the list, but I can't… If you want them too, try to convince the operators to publish their blocks!
(Also, sorry for the downtime Monday & Tuesday, had a big power outage just when I left the house for 2 days…)
I'd like to add BitClockers, ABCPool and NinjaCoin to the list, but I can't… If you want them too, try to convince the operators to publish their blocks!
(Also, sorry for the downtime Monday & Tuesday, had a big power outage just when I left the house for 2 days…)
August 20, 2011, 08:00:26 AM
Do you think it would be difficult to add simplecoin.us? It's not a pool which is trying to hide information and the site is being actively developed but I don't know the API situation. It's been at 50 Gh/s recently so is big enough to be worth considering.
I offer 1 BTC for the addition of this pool.
The developers can be easily contacted here.
I offer 1 BTC for the addition of this pool.
The developers can be easily contacted here.
Okay, done. Now I don't mind you donating 1 BTC for pident developement, but to be honest, I don't think a 5-line commit is worth this
Damn! I didn't know it would be so easy.
Ah well, I'm a man of my word so 1 BTC for you. Enjoy!
August 20, 2011, 06:44:42 AM
Do you think it would be difficult to add simplecoin.us? It's not a pool which is trying to hide information and the site is being actively developed but I don't know the API situation. It's been at 50 Gh/s recently so is big enough to be worth considering.
I offer 1 BTC for the addition of this pool.
The developers can be easily contacted here.
I offer 1 BTC for the addition of this pool.
The developers can be easily contacted here.
Okay, done. Now I don't mind you donating 1 BTC for pident developement, but to be honest, I don't think a 5-line commit is worth this
August 20, 2011, 06:24:11 AM
I tried running this in the past, but whenever I run updateblocks it fails to import, repeatedly spewing out:
PHP Warning: pg_fetch_row() expects parameter 1 to be resource, boolean given in /root/pident/lib/inc.update.php on line 34
PHP Warning: pg_query(): Query failed: ERROR: current transaction is aborted, commands ignored until end of transaction block in /root/pident/lib/inc.update.php on line 100
000015/141657 processing... (00000000b3322c8c3ef7d2cf6da009a776e6a99ee65ec5a32f3f345712238473)PHP Warning: pg_query(): Query failed: ERROR: current transaction is aborted, commands ignored until end of transaction block in /root/pident/lib/inc.update.php on line 33
Can you tell me what version of postgresql you are using?
Thanks.
PHP Warning: pg_fetch_row() expects parameter 1 to be resource, boolean given in /root/pident/lib/inc.update.php on line 34
PHP Warning: pg_query(): Query failed: ERROR: current transaction is aborted, commands ignored until end of transaction block in /root/pident/lib/inc.update.php on line 100
000015/141657 processing... (00000000b3322c8c3ef7d2cf6da009a776e6a99ee65ec5a32f3f345712238473)PHP Warning: pg_query(): Query failed: ERROR: current transaction is aborted, commands ignored until end of transaction block in /root/pident/lib/inc.update.php on line 33
Can you tell me what version of postgresql you are using?
Thanks.
This was solved on IRC, but the problem was using PostgreSQL 8.x (needs version 9 at least).
Jump to: