Pages:
Author

Topic: BiblePay - New Coin Launch - Official Thread - page 89. (Read 119833 times)

newbie
Activity: 27
Merit: 0
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). 



It does seem to be smoothing out a bit. Had a lot more trouble getting my first Windows setup on than my 2nd. My Linux node is now compiling and *crossing fingers* it will join up smoothly and catch up on the correct chain.
Part of the problem was we were banning each other, now the supermajority is taking over again, possibly, God willing.

I dont want to say too much and jinx us.  In the morning lets -reindex and resync a few nodes and verify we didnt store any bad blocks etc.


I noticed that on my Windows machines as well....I actually laughed about it because I saw what was going on and thought "oh, yeah that's the downside to decentralization". I'll run those commands on my nodes in the morning. Glad to be participating in a project like this even in my little way.
newbie
Activity: 8
Merit: 0
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?

First off I in no way meant any disrespect to the Admin or the the teams efforts to make this project a reality! I appreciate their hard work and dedication to this project and I wish it nothing but success. These children can use all the help they can get. I said what I did in an attempt to point out an unequal distribution in the network. It was not meant to be anything more or less.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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). 



It does seem to be smoothing out a bit. Had a lot more trouble getting my first Windows setup on than my 2nd. My Linux node is now compiling and *crossing fingers* it will join up smoothly and catch up on the correct chain.
Part of the problem was we were banning each other, now the supermajority is taking over again, possibly, God willing.

I dont want to say too much and jinx us.  In the morning lets -reindex and resync a few nodes and verify we didnt store any bad blocks etc.
newbie
Activity: 27
Merit: 0
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). 



It does seem to be smoothing out a bit. Had a lot more trouble getting my first Windows setup on than my 2nd. My Linux node is now compiling and *crossing fingers* it will join up smoothly and catch up on the correct chain.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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
Thanks, I sent him a reminder email (ticket still open).
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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). 

full member
Activity: 123
Merit: 111
Happy to be in the Community! Hi Y'all!
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.
full member
Activity: 123
Merit: 111
Happy to be in the Community! Hi Y'all!
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!!!
newbie
Activity: 17
Merit: 0
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. Smiley
newbie
Activity: 27
Merit: 0
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
full member
Activity: 123
Merit: 111
Happy to be in the Community! Hi Y'all!
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"     =)
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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

full member
Activity: 123
Merit: 111
Happy to be in the Community! Hi Y'all!
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. Smiley

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?

full member
Activity: 123
Merit: 111
Happy to be in the Community! Hi Y'all!
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?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.


newbie
Activity: 17
Merit: 0
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. Smiley
newbie
Activity: 8
Merit: 0
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.
newbie
Activity: 17
Merit: 0
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..
full member
Activity: 123
Merit: 111
Happy to be in the Community! Hi Y'all!
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.
hero member
Activity: 906
Merit: 500
Looks like masternode gonna require 500k coins Smiley


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

Buy your coins while you can!
Pages:
Jump to: