BiblePay - New Coin Launch - Official Thread

[p3ppymon]

1st time posting, i been mining this for around 5hours got just over 1k coins, but is still immature balance, how long does it take till its available so i can withdraw ?

This is exactly the question I wanted to ask.
By the way, OP, very good job. Impressive work! I will be following the project closely!

[inblue]

@jamie1989 @p3ppymon
The coins will be available to withdraw after 24 hours.

On the topic of the recent issues, I suspect maybe node.biblepay.org was part of the problem because it changed its IP address recently, but maybe DNS didn't fully propagate for everyone (or the old IP was cached somewhere), and almost everyone has that addnode line in their conf file.

[p3ppymon]

@jamie1989 @p3ppymon
The coins will be available to withdraw after 24 hours.

On the topic of the recent issues, I suspect maybe node.biblepay.org was part of the problem because it changed its IP address recently, but maybe DNS didn't fully propagate for everyone (or the old IP was cached somewhere), and almost everyone has that addnode line in their conf file.

Thanks for the prompt reply. Lastly, is withdrawn working fine? Also, ccex requires ID verification to withdrawn funds?

[inblue]

Thanks for the prompt reply. Lastly, is withdrawn working fine? Also, ccex requires ID verification to withdrawn funds?

Don't withdraw yet, but follow the thread and it will probably sort out in a day or two. For fiat C-Cex probably requires ID verification, but not for BBP - I withdrew BBP with just an email/password account.

[seasonw]

Just tried out both my linux and windows wallets, all are not in correct blockchain, any correct ip given to addnode?

My windows wallet even reverted from 7176 to 7166, maybe error correction...

[gigabyted]

Looks like masternode gonna require 500k coins


https://github.com/biblepay/biblepay/blob/8c9585d0340d6f574aec3b108dd225207735500a/src/activemasternode.cpp#L213

Buy your coins while you can!

[SquidConqueror]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

Thank you dev for keeping us up to date on the issues! =) 

i look forward to things being stable again, as I am sure you are as well.  =)

the wallet will show that I am hashing but the pool show me doing nothing.

[remtiwk]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

the wallet will show that I am hashing but the pool show me doing nothing.

same here..

[bitcoinsrule01]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

the wallet will show that I am hashing but the pool show me doing nothing.

same here..

Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.

Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.

[remtiwk]

So i deleted banlist.dat.. restarted the miner.. and waited a few minutes. Showing up on the pool now finally. Going to try the same with my other machines.

Edit: Got two machines active finally.

[bible_pay]

Oh Shit! I made a withdrawl from the pool before checking this thread! dammit I hope my coins are okay. They haven't arrived in any of my wallets but I can confirm that we are now on multiple forks. The latest version of the client didn't help resolve the problem either..

Sorry guys, got tied up on some more IT issues, what a day huh.

Dont worry about the withdrawal, we will find the coins one way or another.
(Coins are duplicated on forks- so whatever chain ends up having the most work will have your coins.)  The only thing we dont want to do is deposit on a fork to ccex and then have them reorganize, hence why we have to ensure they are offline for maintenance.

It looks like things are starting to come back to normal, the nodes finally agree on a height and the pool is not overloaded.

I need to scan the pool for any back blocks that have not been paid and Ill report back.

[SquidConqueror]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

the wallet will show that I am hashing but the pool show me doing nothing.

same here..

Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.

Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.

A few may be benefiting...but please remember the most that benefit are the orphans and their families that this project supports and reinforces.  The developer is working HARD to get the issues under control.  

It was expected because of the algorithm change.  

Maybe in hindsight just a code change to automatically change block payout and the percentage of the payout to the  cause of donations that this project supports.

While that may seem good...the purpose was to change the algorithm to make it stay resistant to GPU and ASIC...as far as I know.

This "hiccup" is only temporary.  Like I said before....it will be stable again.  I look forward to that.  However sooner or later that may come.

This developer is the most active and understanding of our criticism that I have ever encountered!!!!!!!!

One thing I am not sure of...Are you the only one really running the day to day operations of all of this AWSEOME project?

[SquidConqueror]

So i deleted banlist.dat.. restarted the miner.. and waited a few minutes. Showing up on the pool now finally. Going to try the same with my other machines.

Edit: Got two machines active finally.

I tried...I will try again after a few other things...thank you for pointing us to a solution/possible solution.

What version of the wallet are you using?  1.0.2.9 or 1.0.3.1?

[bible_pay]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

the wallet will show that I am hashing but the pool show me doing nothing.

same here..

Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.

Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.

A few may be benefiting...but please remember the most that benefit are the orphans and their families that this project supports and reinforces.  The developer is working HARD to get the issues under control.  

It was expected because of the algorithm change.  

Maybe in hindsight just a code change to automatically change block payout and the percentage of the payout to the  cause of donations that this project supports.

While that may seem good...the purpose was to change the algorithm to make it stay resistant to GPU and ASIC...as far as I know.

This "hiccup" is only temporary.  Like I said before....it will be stable again.  I look forward to that.  However sooner or later that may come.

This developer is the most active and understanding of our criticism that I have ever encountered!!!!!!!!

One thing I am not sure of...Are you the only one really running the day to day operations of all of this AWSEOME project?

Thanks a lot for the compliments.

Well I have a complicated situation.  I have a little IT consulting company, and we wrote a system used in BPA, but thats winding down to nothing - and as of recently the employee(s) are not actually with me now, so yes, I have a 'little' help, in the sense that I can re-use some of the classes now.  The other situation is I do have a slack team of cryptocurrency programmers but thats all I can say.  That team is not actually working on BiblePay.  Im starting a brand new team for BiblePay.  There is one cryptocurrency programmer that wrote a function for me that I included in the prayer UI (the one that gets the last 7 days of prayers).  So I dont want to take credit for the whole thing and I also dont want to be a lone wolf, as I want this to turn out to be an enterprise project so we can eventually market this to companies who want an alternative 401k investment.

On that note, tomorrow Im looking into creating a new logo contest (by a professional org, not grass roots in this case) for various reasons.
Im thinking of a Latin phrase on the outer edge of the coin:
JUSTIFICATIONE PER FIDEM IN SOCIETATE

[SquidConqueror]

Ok.  Deleting the banlist as previously suggested seems to work.  I do not think I did anything to affect the outcome besides that...I just gave it a little more time after restarting my system.

Windows 7 64bit.  Wallet version 1.0.3.1

the more we comment on particular issues and what we do to help fix them...helps the dev to make our fixes more permanent.

Let's keep this project going...for the reasons it was intended for.  We are a community...let's keep it that way!!   =)


EDIT ------  After about ten minutes I am still posting to the pool.  A lot better than hashing for nothing.

Thank you "remtiwk"     =)

[Shoko943]

I noticed that ccex still has its wallet enabled. Something that worries me is that they're reporting that their block height is 7193 and the pool is at 7223 right now

[remtiwk]

Ok.  Deleting the banlist as previously suggested seems to work.  I do not think I did anything to affect the outcome besides that...I just gave it a little more time after restarting my system.

Windows 7 64bit.  Wallet version 1.0.3.1

the more we comment on particular issues and what we do to help fix them...helps the dev to make our fixes more permanent.

Let's keep this project going...for the reasons it was intended for.  We are a community...let's keep it that way!!   =)


EDIT ------  After about ten minutes I am still posting to the pool.  A lot better than hashing for nothing.

Thank you "remtiwk"     =)

Awesome! Still haven't gotten it working on the 3rd machine, but I have two working at least.

[SquidConqueror]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

the wallet will show that I am hashing but the pool show me doing nothing.

same here..

Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.

Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.

A few may be benefiting...but please remember the most that benefit are the orphans and their families that this project supports and reinforces.  The developer is working HARD to get the issues under control.  

It was expected because of the algorithm change.  

Maybe in hindsight just a code change to automatically change block payout and the percentage of the payout to the  cause of donations that this project supports.

While that may seem good...the purpose was to change the algorithm to make it stay resistant to GPU and ASIC...as far as I know.

This "hiccup" is only temporary.  Like I said before....it will be stable again.  I look forward to that.  However sooner or later that may come.

This developer is the most active and understanding of our criticism that I have ever encountered!!!!!!!!

One thing I am not sure of...Are you the only one really running the day to day operations of all of this AWSEOME project?

Thanks a lot for the compliments.

Well I have a complicated situation.  I have a little IT consulting company, and we wrote a system used in BPA, but thats winding down to nothing - and as of recently the employee(s) are not actually with me now, so yes, I have a 'little' help, in the sense that I can re-use some of the classes now.  The other situation is I do have a slack team of cryptocurrency programmers but thats all I can say.  That team is not actually working on BiblePay.  Im starting a brand new team for BiblePay.  There is one cryptocurrency programmer that wrote a function for me that I included in the prayer UI (the one that gets the last 7 days of prayers).  So I dont want to take credit for the whole thing and I also dont want to be a lone wolf, as I want this to turn out to be an enterprise project so we can eventually market this to companies who want an alternative 401k investment.

On that note, tomorrow Im looking into creating a new logo contest (by a professional org, not grass roots in this case) for various reasons.
Im thinking of a Latin phrase on the outer edge of the coin:
JUSTIFICATIONE PER FIDEM IN SOCIETATE

You are more than welcome for the compliments!  You deserve them.  I am quite sure that you have given more than you have gotten from this project so far.  As I know that was your intentions in the first place.  Anything great never comes without triumphs and tribulations.  The world needs to be about giving more that taking/receiving. We would be so much better off!



PEOPLE over profit!!!

[SquidConqueror]

I figured you were like a chicken on a farm with it's head cutoff....running around juggling life and crypto!

I commend you...I just wish I would of kept up with coding so that I could help you out.

Reach out to the Community if needed...I am sure one of us...two if you are lucky....can lend some fingers and brain power to the situation.

[bible_pay]

So auditing the pools activity since block 7000, we had One block (7143) that appeared on the surface to be paid @ 0.
This block was orphaned, the pool didnt get it.  I deleted the records for it.

You can verify this by typing : run subsidy 7143.  The pools address is  the one found on 7139 (b6j). 
I dont see any other discrepencies (other than wildly fluctuation hashes due to people dropping in/out of the pool etc).