I still haven't figured out what's tripping up those scanners, they don't give much information. The package contains an NSIS installer, the visual c++ 2015 runtime and the RaiBlocks executable. One of them must match whatever signature they use. |
|
|
|
Yes right now it's behind schedule, I'm finishing up on a GPU module which should make the faucet more responsive, the system has a small pow generated by the transaction creator which rate limits transactions and sometimes the faucet gets back logged due to volume. When we increase the rate no doubt it'll attract more people so we don't want it to be even less responsive.
Does this mean that you plan to increase the amount that the faucet is paying? Great project by the way, keeping an eye on it! Yep. Thanks watching! |
|
|
|
That's the one, thanks for helping. I'll get that added to the downloads page. |
|
|
|
Where can I download that wallet?
I want to get my wallet synch alot faster, will the new wallet help?
I can not find the file...
https://raiblocks.net/#/startIt should synchronize faster, some people have tried already and it worked better, let me know. |
|
|
|
I have 2 questions.
According to Distribution scheldule, we hae to complele 50% in first year and only few months left in first year and we are only 2.8% distriputed.
Is it time to increase the faucet to 1000 or 500 each claim so that we may reach the target and also benefit the early adotpters ?
Distribution schedule:
Year 1: 2^127 50%
Year 2: 2^126 25%
Year 3: 2^125 13%
Year 4: 2^124 6.3%
Year 5: 2^123 3.1%
Year 6: 2^122 1.6%
Year 7: 2^121 0.8%
Year 8: 2^121 0.8%
Question no 2:
So when this will really be on the exchanges ? once all distribution is done ?? after 8 years ?? 2024 ?
Yes right now it's behind schedule, I'm finishing up on a GPU module which should make the faucet more responsive, the system has a small pow generated by the transaction creator which rate limits transactions and sometimes the faucet gets back logged due to volume. When we increase the rate no doubt it'll attract more people so we don't want it to be even less responsive. Being in exchanges is less of our choice and more of the choice of the exchange operators. From our perspective sooner would be better because it makes everything more useful to people. Exchange operators typically want to see a technical contribution and not just Bitcoin Clone #3141, then want to make sure their users aren't going to be scammed, and they want to see established interest for volume. I think we satisfy those so hopefully we can get listed. One thing that irritates exchanges is people excessively shilling for it so we try to avoid that. |
|
|
|
Hello, I tried to claim the faucet onces and it keeps saying queuing. What does it not send to my wallet?
My wallet is synched.
It might be a little slow at the moment, it looks like the load is high because a lot of people are going to the faucet. I'm just about done with an GPU module that will offload work generation and let it all go a lot faster. |
|
|
|
your faucet uses point time of browsers, i'm get coins - close browser, n min left (n >1) open and click "Request" and see "Wait n seconds" when n - is seconds to close browser. if you want all distributed at site 8 years, you need to fix it
That's intentional, otherwise people would close and open their browser to get them faster. |
|
|
|
How long is it supposed to sync?
There's a bug where it's taking longer than it needs to. I hope to patch it tonight. |
|
|
|
we spoke about faucet and now is not working anymore!
Seems like it's working, people are getting them right now. |
|
|
|
Was better to give chance for early adopter to get at list 1000 facucet , than every month less!
I think we're all early adopters since less than 3% is distributed. I think the people that will benefit the most are those who can make use of the features, especially the ones that can't be reached by other platforms. I focused on micropayments because I think this is a market that people want but hasn't been possible with either traditional payments or Bitcoin. Traditional payments have fees that are too high and Bitcoin has a hard time with realtime processing like clearing ads off a page while a user waiting. I think this can be done now. so sometime the faucet will be less? Eventually the faucet will be off because 100% will be distributed. We're trying to hit this schedule so we'll adjust the faucet amount to stay on schedule. https://github.com/clemahieu/raiblocks/wiki/Distribution-and-Mining |
|
|
|
Was better to give chance for early adopter to get at list 1000 facucet , than every month less!
I think we're all early adopters since less than 3% is distributed. I think the people that will benefit the most are those who can make use of the features, especially the ones that can't be reached by other platforms. I focused on micropayments because I think this is a market that people want but hasn't been possible with either traditional payments or Bitcoin. Traditional payments have fees that are too high and Bitcoin has a hard time with realtime processing like clearing ads off a page while a user waiting. I think this can be done now. |
|
|
|
Does the client have to be running for the faucet transaction to complete?
No. The faucet will create the send block and the ledger will mark it as receivable by your account. When you turn your wallet on and unlock it, it'll search for receivables and sign acceptances in your chain at which point your balance will increase. I have a work item to count and track receivable balance since some people wonder why their balance hasn't increased when someone sends to them and their signing key is offline. Nothing is lost though. |
|
|
|
if the wallet of the recipient sends the network a signature of the input transaction, then you can track the start time of the wallet? rightly or no?
The wallet also needs to be unlocked otherwise it doesn't have access to the signing key. You could guess if a wallet was unlocked or turned on if you see a burst of receives for a single account. Is this was you mean? If this is concerning it seems like it could be coded to wait random amounts of time to obfuscate it. I mean that the block chain contains the time of signing the Inbox (when the recipient sees this) of a transaction or not? or this information does not contain in signature? I see, there are no time stamps in the block chain. |
|
|
|
if the wallet of the recipient sends the network a signature of the input transaction, then you can track the start time of the wallet? rightly or no?
The wallet also needs to be unlocked otherwise it doesn't have access to the signing key. You could guess if a wallet was unlocked or turned on if you see a burst of receives for a single account. Is this was you mean? If this is concerning it seems like it could be coded to wait random amounts of time to obfuscate it. |
|
|
|
my wallet can't connect the stat's always synchronizing   There is a bug where it stays synchronizing longer than it should due to tcp timeouts. I have a patch almost done that I'll release tonight. Eventually it should complete but it takes much longer than it needs to. |
|
|
|
For the record - seems to be working now. I'll try to not do more than one per minute.  Glad to hear it and for sure, the intent of this is for people to be able to some each day and allow new people to get a small amount to play around with it; I think that's one feature that's lacking in traditional mining, easy access. We did add the timer on the button which we're hoping will give a better user experience than just "try later". What we don't want is the faucet to become is a day job, botted, or farmed even though we know that's a pretty ambitious goal, we'll see. |
|
|
|
instalation success, but the status always synchronizing. same issue but on 64 bit Ill put together a patch release to address this issue, it's appearing as more nodes appear in the network. Eventually it should sync but it takes much longer than it should. I'll put it out either today or tomorrow. |
|
|
|
|
Show Posts
