I clicked on the explorer but I did not see it,
For the lottery block what is the recommend size?
Is it per address or per wallet?
Check OP
To my knowledge, it's per wallet. 
Topic: [ANN][BTX] Bitcoin - The NeXt Generation /NEW ANN and WEBSITE ! - page 43. (Read 83738 times)
I clicked on the explorer but I did not see it,
For the lottery block what is the recommend size?
Is it per address or per wallet?
Check OP
To my knowledge, it's per wallet. 
I clicked on the explorer but I did not see it,
For the lottery block what is the recommend size?
Is it per address or per wallet?
Do we have rich list?
please retweet guys! https://twitter.com/btxcoin/status/597454661692628992
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
It worked just fine when I used it.
Success! You have been awarded with 7.4959 BTX!
Love that faucet, looks really good
lol yeah everyone was finding lucky blocks the way the BT scam team had it, but guess what? that means they weren't so lucky now were they?
really you people are bitching they haven't found 1 of the rare 2% blocks? and having to have the right funds to qualify on that block means it'll be much less than 2% of a chance
(10k had a 2% chance, and I'd find 20-30 blocks a day and if I was lucky every 2nd or 3rd day I'd find a lucky block)
I haven't had any syncing issues since I added all the nodes from the OP.
hopefully the coins are in stronger hands now
really you people are bitching they haven't found 1 of the rare 2% blocks? and having to have the right funds to qualify on that block means it'll be much less than 2% of a chance
(10k had a 2% chance, and I'd find 20-30 blocks a day and if I was lucky every 2nd or 3rd day I'd find a lucky block)
I haven't had any syncing issues since I added all the nodes from the OP.
hopefully the coins are in stronger hands now
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
It worked just fine when I used it.
Success! You have been awarded with 7.4959 BTX!
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
It worked just fine when I used it.
Looks like payouts are working too.... someone just 6.9.... second payout.... cool
"Success! You have been awarded with 6.9928 BTX!" ))
VERY, VERY COOL!!
Thanks for letting me know
WE NOW HAVE A TWITTER ACCOUNT:
https://twitter.com/btxcoin
https://twitter.com/btxcoin
Looks like payouts are working too.... someone just 6.9.... second payout.... cool
"Success! You have been awarded with 6.9928 BTX!" ))
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
ping and tracert ok
but browser
ERR_CONNECTION_TIMED_OUT
Can you give it a try now?
Tested through a wireless broadband connection successfully just now.
Thanks for the info... let me take a look at the iptables and possibly reboot...
IT WORKS !!!
COOL!!!!
That will teach me to have so many firewalls!!!
Looks like payouts are working too.... someone just 6.9.... second payout.... cool
Missing lucky stakes?
According to my analysis, the following blocks should have generated lucky stakes if the input coins were > 50k, 100k, or 300k;
5959
5965
5950
5865
5754
5800
5727
5730
5960
5844
5971
5794
The first group, in red, all had inputs large enough but generated normal stakes. The one in the middle is the only one that lucky staked. The third group all had inputs too small.
There's probably a simple explanation, something obvious I'm just not seeing but is anybody able to explain why, based on the code in github, the blocks in red did not produce lucky stakes?
According to my analysis, the following blocks should have generated lucky stakes if the input coins were > 50k, 100k, or 300k;
5959
5965
5950
5865
5754
5800
5727
5730
5960
5844
5971
5794
The first group, in red, all had inputs large enough but generated normal stakes. The one in the middle is the only one that lucky staked. The third group all had inputs too small.
There's probably a simple explanation, something obvious I'm just not seeing but is anybody able to explain why, based on the code in github, the blocks in red did not produce lucky stakes?
PM this to dev.
They probably weren't lucky. Remember, chance is only 2%.
2% were chosen to prevent inflation, but I can change to whatever arbitrary number community chooses.
Let's make it 5% if it is not too much hassle.
Missing lucky stakes?
According to my analysis, the following blocks should have generated lucky stakes if the input coins were > 50k, 100k, or 300k;
5959
5965
5950
5865
5754
5800
5727
5730
5960
5844
5971
5794
The first group, in red, all had inputs large enough but generated normal stakes. The one in the middle is the only one that lucky staked. The third group all had inputs too small.
There's probably a simple explanation, something obvious I'm just not seeing but is anybody able to explain why, based on the code in github, the blocks in red did not produce lucky stakes?
According to my analysis, the following blocks should have generated lucky stakes if the input coins were > 50k, 100k, or 300k;
5959
5965
5950
5865
5754
5800
5727
5730
5960
5844
5971
5794
The first group, in red, all had inputs large enough but generated normal stakes. The one in the middle is the only one that lucky staked. The third group all had inputs too small.
There's probably a simple explanation, something obvious I'm just not seeing but is anybody able to explain why, based on the code in github, the blocks in red did not produce lucky stakes?
PM this to dev.
They probably weren't lucky. Remember, chance is only 2%.
2% were chosen to prevent inflation, but I can change to whatever arbitrary number community chooses.
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
ping and tracert ok
but browser
ERR_CONNECTION_TIMED_OUT
Can you give it a try now?
Tested through a wireless broadband connection successfully just now.
Thanks for the info... let me take a look at the iptables and possibly reboot...
Can you give it a try now?
Tested through a wireless broadband connection successfully just now.
IT WORKS !!!
COOL!!!!
That will teach me to have so many firewalls!!!
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
ping and tracert ok
but browser
ERR_CONNECTION_TIMED_OUT
Can you give it a try now?
Tested through a wireless broadband connection successfully just now.
Thanks for the info... let me take a look at the iptables and possibly reboot...
Tested through a wireless broadband connection successfully just now.
IT WORKS !!!
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
ping and tracert ok
but browser
ERR_CONNECTION_TIMED_OUT
Tested through a wireless broadband connection successfully just now.
Strange, I just opened it from the link you quoted... let me check it further
Can someone else check it also
ping and tracert ok
but browser
ERR_CONNECTION_TIMED_OUT
Thanks for the info... let me take a look at the iptables and possibly reboot...
Missing lucky stakes?
According to my analysis, the following blocks should have generated lucky stakes if the input coins were > 50k, 100k, or 300k;
5959
5965
5950
5865
5754
5800
5727
5730
5960
5844
5971
5794
The first group, in red, all had inputs large enough but generated normal stakes. The one in the middle is the only one that lucky staked. The third group all had inputs too small.
There's probably a simple explanation, something obvious I'm just not seeing but is anybody able to explain why, based on the code in github, the blocks in red did not produce lucky stakes?
According to my analysis, the following blocks should have generated lucky stakes if the input coins were > 50k, 100k, or 300k;
5959
5965
5950
5865
5754
5800
5727
5730
5960
5844
5971
5794
The first group, in red, all had inputs large enough but generated normal stakes. The one in the middle is the only one that lucky staked. The third group all had inputs too small.
There's probably a simple explanation, something obvious I'm just not seeing but is anybody able to explain why, based on the code in github, the blocks in red did not produce lucky stakes?
PM this to dev.
In the spirit of openness can he not respond here?
To be honest I dumped my 400k when I discovered this morning that it had staked one of those blocks in red and got 2.xx BTX. I wish you all luck with it but there have just been too many issues with this coin for me to keep the faith. It's not just BTX, that was the final straw though... I dumped every altcoin I had this morning, too many scams and no real world adoption and I've got too much else to concentrate on.
Boy IDK. In still staking my 236,000, but wallet keeps going out of sync, and I've tried everything, including CryptoClub's suggestion. Never had so many problems with keeping a wallet in sync, and now lucky staking might not be working? Will keep holding but not sure for how much longer.
To my knowledge, there is 0 issue with the coin. It's just the way PoS works. Next wallet may improve that. If you doubt, please dump. We will gladly buy your cheap coins.
What we are creating here is greatly larger in scope than Lucky Blocks or Masternodes. If you cannot wait a few weeks to see how far we are planning to go, then too bad for you.
Seriously give me a break. I won't be dumping because why at this point? Unless I want to get 10% back on my "investment". Simply stating that I've never seen a wallet with so many syncing issues, and let me tell you that in the past year that I've been buying coins, I've put BTC into some seriously fucked up coins, but hey... at least their wallet's stayed in sync lol Can't understand why my wallet won't stay in sync, even though I've tried everything. Who knows. Maybe it's my internet connection, not sure. Although every other coin up to this point worked fine. Now wallet says "not staking because wallet is offline." Great. Oh well.
kpierce, do not feel abandoned
BTXdev or PrometheusX will help you tomorrow.
Today is Sunday and Mother's day
Jump to: