|
oldcoinguru
|
 |
July 19, 2017, 04:47:25 PM |
|
Anyone have any idea what's going on with Cryptopia? The wallet is disabled and there is a message about a possible fork.
Hmm, I don't see anything on the site about a fork. Do you get that message when you're logged in? If you go to the wallet and try to withdraw coins the link to withdraw is grayed out and a popup states that the wallet is in maintenance while they investigate a possible fork. I also noticed that the block explorers at chainradar and minergate are down for Boolberry. Oh well. I guess my coins are stuck at cryptopia. |
|
|
|
|
|
b4h4mu7
|
|
July 19, 2017, 05:02:26 PM |
|
Anyone have any idea what's going on with Cryptopia? The wallet is disabled and there is a message about a possible fork.
Hmm, I don't see anything on the site about a fork. Do you get that message when you're logged in? If you go to the wallet and try to withdraw coins the link to withdraw is grayed out and a popup states that the wallet is in maintenance while they investigate a possible fork. I also noticed that the block explorers at chainradar and minergate are down for Boolberry. Oh well. I guess my coins are stuck at cryptopia. Ok. I'll contact them and try to resolve the issue. Yes, both chainradar and minergate are down again. If everyone can try to send them a message asking them resolve it that would help out. |
|
|
|
|
|
b4h4mu7
|
|
July 19, 2017, 05:15:29 PM
Last edit: July 19, 2017, 05:31:02 PM by b4h4mu7 |
|
If someone from the community wants to setup and maintain a block explorer, I'll compensate them with a bounty. 500XBB seems reasonable.
|
|
|
|
|
|
1blockologist
|
|
July 19, 2017, 09:38:04 PM |
|
both chainradar and minergate are down again
this shit again? are there any actual diagnostics on the network? what are your daemons saying |
|
|
|
|
b4h4mu7
|
|
July 19, 2017, 11:02:20 PM |
|
If someone from the community wants to setup and maintain a block explorer, I'll compensate them with a bounty. 500XBB seems reasonable.
Thanks for the interest everyone. Bounty is being claimed. We should have an explorer up soon. |
|
|
|
|
|
tljenson
|
|
July 28, 2017, 12:17:23 AM |
|
Does anybody want some free Boolberry? I'm trying to clean out my wallets on Bittrex and can't sell it. I only have 0.98910000, but would be happy to send it to you. Just leave you Boolberry address.
|
|
|
|
|
|
cherry11800
|
|
July 28, 2017, 12:23:30 AM |
|
What is the new development for this coin?
|
|
|
|
|
|
|
|
crypjunkie
|
|
July 28, 2017, 08:58:30 PM |
|
If someone from the community wants to setup and maintain a block explorer, I'll compensate them with a bounty. 500XBB seems reasonable.
Thanks for the interest everyone. Bounty is being claimed. We should have an explorer up soon. Can you contact me plz. |
|
|
|
|
|
crypjunkie
|
|
July 28, 2017, 09:01:49 PM |
|
both chainradar and minergate are down again
this shit again? are there any actual diagnostics on the network? what are your daemons saying 1Block ya gonna help out again? You did say if the liquidity was there you would come back! If b4h4mu7 is serious about technical developments and has an active developer helping out we can bring some additional help and benefits for everyone. |
|
|
|
|
|
clintar2
|
|
July 30, 2017, 03:23:23 PM
Last edit: July 30, 2017, 05:06:11 PM by clintar2 |
|
I have my block explorer up and running at http://explorer.mining.blue/en. It's still in development so don't trust it to be giving accurate info, but I figure it's something at least for now. Please help by letting me know of anything that seems off so I can fix it. It's based on code written for Karbowanec and I've attempted to make equivalent rpc calls in boolberry to get it working here, but unsure about how I've translated some of that. |
|
|
|
|
|
b4h4mu7
|
|
July 30, 2017, 05:03:11 PM |
|
I have my block explorer up and running at http://explorer.mining.blue. It's still in development so don't trust it to be giving accurate info, but I figure it's something at least for now. Please help by letting me know of anything that seems off so I can fix it. It's based on code written for Karbowanec and I've attempted to make equivalent rpc calls in boolberry to get it working here, but unsure about how I've translated some of that.  |
|
|
|
|
|
cherry11800
|
|
July 31, 2017, 02:07:14 PM |
|
Thank you for this information,Do you know what information is there for DEV? :)After Delist on polo ,The community is not very active |
|
|
|
|
|
1blockologist
|
|
July 31, 2017, 09:07:49 PM |
|
both chainradar and minergate are down again
this shit again? are there any actual diagnostics on the network? what are your daemons saying 1Block ya gonna help out again? You did say if the liquidity was there you would come back! If b4h4mu7 is serious about technical developments and has an active developer helping out we can bring some additional help and benefits for everyone. exactly, its not out of the question! for now I'll just provide infrastructure where I can |
|
|
|
|
clintar2
|
|
August 01, 2017, 05:52:15 AM |
|
Ok, just an update on the explorer http://explorer.mining.blue/en. I got most things working now. I removed things we don't keep track of for this coin. Again, let me know of anything that looks to be wrong., but It should be pretty useful now. Have a great day! |
|
|
|
|
rbrunner7
Newbie
 Offline
Activity: 7
Merit: 0
|
|
August 01, 2017, 07:55:12 AM |
|
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)
It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.
But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.
What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?
Or still something not quite right with my new node?
|
|
|
|
|
|
clintar2
|
|
August 01, 2017, 11:37:41 PM
Last edit: August 02, 2017, 04:20:39 AM by clintar2 |
|
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)
It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.
But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.
What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?
Or still something not quite right with my new node?
Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now. |
|
|
|
|
rbrunner7
Newbie
Offline
Activity: 7
Merit: 0
|
|
August 02, 2017, 08:19:11 PM |
|
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)
...
But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.
...
Or still something not quite right with my new node?
Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now. Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend. But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ... By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me. |
|
|
|
|
|
clintar2
|
|
August 03, 2017, 12:09:02 AM |
|
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)
...
But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.
...
Or still something not quite right with my new node?
Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now. Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend. But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ... By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me. No, here is fine. |
|
|
|
|
b3da
Member
Offline
Activity: 94
Merit: 10
|
|
August 06, 2017, 04:53:17 AM |
|
its great to have working block explorer again. thank you! |
|
|
|
|
