Search content
Sort by
Showing 20 of 27 results by jamilservicos
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
I wonder if faucet "developers" make test before on in production environment!
Because I really do not believe they do not realize the obvious problems!
Because I really do not believe they do not realize the obvious problems!
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
I see these people saying "scam" and I give a lot of laughter ...
Do you at least know what "scam" is
Has anyone invested money in the faucet to categorize it as a "scam"?
The website is out of the air, ok! you will not be able to win xrb free ... just this!
If you want it that much, then buy from "exchange"!
the bot owners who abused the faucet are selling thousands of xrb in the "exchanges"!
stop scandals, if the site is offline, it's because they're in trouble!
Do you at least know what "scam" is
Has anyone invested money in the faucet to categorize it as a "scam"?
The website is out of the air, ok! you will not be able to win xrb free ... just this!
If you want it that much, then buy from "exchange"!
the bot owners who abused the faucet are selling thousands of xrb in the "exchanges"!
stop scandals, if the site is offline, it's because they're in trouble!
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
Excelente Desarrolladores <3 son los mejores
Así como una persona canta canciones en otro idioma sólo por el sonido fonetico, aprender de 0 a 9 también es fácil.
Sólo tienes que acostumbrarse al sonido ... y puedes usar el google translator para escuchar los números en otra lengua.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
You make audio captcha, deaf people complain. If you come back to the good old 6 letters, blind one gonna whine. The numbers are in english, spanish guys cry. If you listen to them and make numbers spanish, arabic ones gonna yell. Enough now, come on... 
the faucet is in English it is normal for the audio to be in English!
and learning from 0 to 9, in another language is not so difficult. Just write the numbers with the sound of them in an paper.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
Sincerely ... i can not listen ... not to mention the loud noise that can cause hearing problems.
Remember that this is a proof of being human and not bot!
So do something for humans!
The idea is good, but it is inaudible!
Remember that this is a proof of being human and not bot!
So do something for humans!
The idea is good, but it is inaudible!
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
I do not like not knowing my actual amount of claims, with so many autofresh and delays, I have no way of knowing if the system is counting, or how much I still need to reach the payment.
I only see the minimum going up!
I recommend the release of personal claims.
"https://faucet.raiblockscommunity.net/paylist.php?acc=xrb_...."
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
Threshold - 5700 !, Dev Kill the bots! 
https://www.youtube.com/watch?v=GpdRXg7nO4U
https://www.youtube.com/watch?v=kiL0efr0Viw
https://www.youtube.com/watch?v=MfmeazQlMUE
https://www.youtube.com/watch?v=GpdRXg7nO4U
https://www.youtube.com/watch?v=kiL0efr0Viw
https://www.youtube.com/watch?v=MfmeazQlMUE
video 1: Old model, recorded before solvemedia
video 2: Old bug
video 3: Despite being the most current of all the videos mentioned, is also an old video.
Errors are currently punished, and there are some innovations in the system.
But of course it would be much harder for a bot to outgrow a human being if the secure virtual keyboard system was in implemented.
About the videos above .... recommend before anything ... check the verity of the sources .... because that is how you sell a product that does not work ... with a misleading advertisement ...
To denounce any use, any video, or failure .. use current evidence ... and not of old versions.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
First I would like to congratulate the faucet team, it seems to me that after several attempts, finally found the way to successfully control abuse via backend.
But since they chose to keep the current difficulty of captcha, instead of diminishing and using a safe and dynamic virtual keyboard.
I have one more one recommendation to make the faucet more friendly to humans.
Instead of using:
"BCDEGKMNPQUVXY36789"
Could modify to:
"BCDEFGRSQTVWXZ16789"
This would allow the use of the numerical keyboard, making it friendlier for those who do not have much experience typing, making the faucet more comfortable, since it will not need big displacements reducing the physical effort of the hands.
I still consider the mix of claims from the previous round to the new one, something that needs to be changed, with pauses for payments.
Currently the claims of the previous rank, and the payment has a delay of 15 - 20 min, which makes the beginning of the new round a part of the last.
The pauses would still allow greater control over the rise and fall of the "Threshold", which can rise exponentially in cases of new abuse.
As soon as the "Threshold" has a controlled value, it could be scheduled. Per example: 100blocks or 1000blocks
This would increase the Threshold's flexibility, which is based on an automatic average on rank.
=================================================
Now about the source of the raiblocks and their constantly reported problems, I believe you need to take a new path.
There are many included dependencies that are outdated for at least 2 years.
Updates are performed to correct faults, and if you wish to use external modules in your codes, you must follow the updates and their codes.
This will allow for greater flexibility in future versions of your client.
I strongly recommend not to edit external modules, but to create an internal module that can work with the external module, without having to move the rest of the code. Changing only the communication modules between A and B.
But since they chose to keep the current difficulty of captcha, instead of diminishing and using a safe and dynamic virtual keyboard.
I have one more one recommendation to make the faucet more friendly to humans.
Instead of using:
"BCDEGKMNPQUVXY36789"
Could modify to:
"BCDEFGRSQTVWXZ16789"
This would allow the use of the numerical keyboard, making it friendlier for those who do not have much experience typing, making the faucet more comfortable, since it will not need big displacements reducing the physical effort of the hands.
I still consider the mix of claims from the previous round to the new one, something that needs to be changed, with pauses for payments.
Currently the claims of the previous rank, and the payment has a delay of 15 - 20 min, which makes the beginning of the new round a part of the last.
The pauses would still allow greater control over the rise and fall of the "Threshold", which can rise exponentially in cases of new abuse.
As soon as the "Threshold" has a controlled value, it could be scheduled. Per example: 100blocks or 1000blocks
This would increase the Threshold's flexibility, which is based on an automatic average on rank.
=================================================
Now about the source of the raiblocks and their constantly reported problems, I believe you need to take a new path.
There are many included dependencies that are outdated for at least 2 years.
Updates are performed to correct faults, and if you wish to use external modules in your codes, you must follow the updates and their codes.
This will allow for greater flexibility in future versions of your client.
I strongly recommend not to edit external modules, but to create an internal module that can work with the external module, without having to move the rest of the code. Changing only the communication modules between A and B.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
Already says the saying "know your enemy first of all".
So for all who think that increasing the difficulty of captcha will prevent bots, thinking that we are still in the era of bots ocr.
I ask you ... Do you understand how these captchas bots work? Do you know the purpose of your initial creation?
Initially the bots were created with the purpose of assisting disabled people with embedded programs, plugins, extensions that could read and / or solve captchas.
As the captchas were simple, the first bots and services used with ocr for captcha recognition.
The idea was copied by misinformed people who started selling automated captcha resolution services for spam purposes.
Just as the captchas system evolved, automation services also ...
Today these services that charge by amount and monthly, pay people per captcha resolved within your site.
Then a bot works as follows ...
It recognizes the captcha and sends it to a server, the server receives and queues it in pool of resolution, where there are dozens, or even hundreds of people solving captchas every second. When the captcha is resolved it is sent back to the requester, and automatically placed in the response input.
When the solution is sent, it is validated by the program, plugin, bot and returns with right or wrong to the server, it pays the person who solved, or punished the error.
Nowadays, bots are only remote people. Then the difficulty of captcha itself, not for the bots, but the people ... if it is possible for a person to read, the bot will read.
Increasing the difficulty for people, for the purpose of stopping the bots, is simply to make your system accessible only by bots. Which has several people to try to solve.
While the average user will just give up trying.
And that's exactly why the new version of recaptcha has no more difficulty, it only validates backend.
When a developer thinks about system security, he first needs to understand how the most common attacks work.
In the case of captchas bots, it uses multi tabs resolved by remote people at the same time.
Therefore the solution is the limitation of validations per min of each wallet. Ip does not work simply by being easily changed in adsl connections and proxys
And of course changing fixed ids and fixed function names would also hamper the automated imput, since the code would be obfuscated by ids and dynamic names created during the rendering;
The issue is not increasing the difficulty of viewing the captcha, but the backend validation and reading the source code.
So for all who think that increasing the difficulty of captcha will prevent bots, thinking that we are still in the era of bots ocr.
I ask you ... Do you understand how these captchas bots work? Do you know the purpose of your initial creation?
Initially the bots were created with the purpose of assisting disabled people with embedded programs, plugins, extensions that could read and / or solve captchas.
As the captchas were simple, the first bots and services used with ocr for captcha recognition.
The idea was copied by misinformed people who started selling automated captcha resolution services for spam purposes.
Just as the captchas system evolved, automation services also ...
Today these services that charge by amount and monthly, pay people per captcha resolved within your site.
Then a bot works as follows ...
It recognizes the captcha and sends it to a server, the server receives and queues it in pool of resolution, where there are dozens, or even hundreds of people solving captchas every second. When the captcha is resolved it is sent back to the requester, and automatically placed in the response input.
When the solution is sent, it is validated by the program, plugin, bot and returns with right or wrong to the server, it pays the person who solved, or punished the error.
Nowadays, bots are only remote people. Then the difficulty of captcha itself, not for the bots, but the people ... if it is possible for a person to read, the bot will read.
Increasing the difficulty for people, for the purpose of stopping the bots, is simply to make your system accessible only by bots. Which has several people to try to solve.
While the average user will just give up trying.
And that's exactly why the new version of recaptcha has no more difficulty, it only validates backend.
When a developer thinks about system security, he first needs to understand how the most common attacks work.
In the case of captchas bots, it uses multi tabs resolved by remote people at the same time.
Therefore the solution is the limitation of validations per min of each wallet. Ip does not work simply by being easily changed in adsl connections and proxys
And of course changing fixed ids and fixed function names would also hamper the automated imput, since the code would be obfuscated by ids and dynamic names created during the rendering;
The issue is not increasing the difficulty of viewing the captcha, but the backend validation and reading the source code.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
@jayycox
I thank you for your response, and I will not lengthen other points, so as not to appear rude to some people on the development team. But I would like to ask attention you for a point that I considered critical regarding support.
When I met the raiblocks, it was through the site "claimers.io", because I am always researching and testing sites involved with cryptocurrent, and I have been following some icos that I consider interesting.
And then I thought about dividing my claims time with a friend, and then I asked here in the forum about team, and they told me that it was enough to only share the same address.
But that leaves a question ... how to control the exact number of claims for a fair division of the prize?
So I looked for your support channel.
I had clarified that I was creating a system to be able to control the number of claims, and that it could perform an automatic division based on the number of claims of each.
But I had not found any way to track the claims, and I had already studied the "pool code" on your site and found nothing of the sort.
I received as an answer from an admin in the group: "pool is forbidden, these your question refers to a prohibited practice". And everything I typed was deleted
And then I replied: "If pool is forbidden, why the source code to create pool, is available on the official website? I recommend an update in the section of the site."
I also commented that I was not trying to create a pool, but a way to track the claims.
Then I received the answer: "This channel is for support of the" raiblocks "and not for the" faucet ". And everything I typed was deleted again.
And then I commented: "This is the support channel available on the official website and in the "faucet", if you can does not respond with "faucet" integration, I recommend to remove your "support channel" from the "faucet" site."
And everything I typed was deleted again. And I was ignored!
It is really difficult to show a code, when development issues are handled in this way ... And the site does not have api information, or integrations ...
I actually got discouraged in developing any line in github after that treatment.
Another day in the" telegram group", I was talking about the problem of the bots, and I said that if it continues then the coin will end up becoming worthless. And the solution would be another cryptocoin. And I was banned of group!
With that kind of behavior of those who should listen, and help others. It's really hard!
In fact this behavior arouses contempt of many, and even comes to be grounds for attacks of "DDOS" for others.
We live a reality that BOTs can no longer be ignored, nor does it successfully recaptcha in this regard.
But we can control them ...
It does not matter if a person uses bots or not, as long as they do not have an advantage over a person who does not use ... Limitations are necessary, so that the bots do not exceed the "humanly possible".
And so it will have equality, because if a person can follow a bot, there will be no advantage of the bot on the person.
"60 claims per minute? team or bot only!
only 1ip per claim/minute? only bots then"
Increase the top, will not solve, increase the difficulty of the captcha will not solve. The solution is in the backend. Validations and limitations need to be reviewed in the backend.
I thank you for your response, and I will not lengthen other points, so as not to appear rude to some people on the development team. But I would like to ask attention you for a point that I considered critical regarding support.
When I met the raiblocks, it was through the site "claimers.io", because I am always researching and testing sites involved with cryptocurrent, and I have been following some icos that I consider interesting.
And then I thought about dividing my claims time with a friend, and then I asked here in the forum about team, and they told me that it was enough to only share the same address.
But that leaves a question ... how to control the exact number of claims for a fair division of the prize?
So I looked for your support channel.
I had clarified that I was creating a system to be able to control the number of claims, and that it could perform an automatic division based on the number of claims of each.
But I had not found any way to track the claims, and I had already studied the "pool code" on your site and found nothing of the sort.
I received as an answer from an admin in the group: "pool is forbidden, these your question refers to a prohibited practice". And everything I typed was deleted
And then I replied: "If pool is forbidden, why the source code to create pool, is available on the official website? I recommend an update in the section of the site."
I also commented that I was not trying to create a pool, but a way to track the claims.
Then I received the answer: "This channel is for support of the" raiblocks "and not for the" faucet ". And everything I typed was deleted again.
And then I commented: "This is the support channel available on the official website and in the "faucet", if you can does not respond with "faucet" integration, I recommend to remove your "support channel" from the "faucet" site."
And everything I typed was deleted again. And I was ignored!
Quote
The best way to get involved in raiblocks is by doing something, write code, design a logo, make something - actions speak louder then words
It is really difficult to show a code, when development issues are handled in this way ... And the site does not have api information, or integrations ...
I actually got discouraged in developing any line in github after that treatment.
Another day in the" telegram group", I was talking about the problem of the bots, and I said that if it continues then the coin will end up becoming worthless. And the solution would be another cryptocoin. And I was banned of group!
With that kind of behavior of those who should listen, and help others. It's really hard!
In fact this behavior arouses contempt of many, and even comes to be grounds for attacks of "DDOS" for others.
We live a reality that BOTs can no longer be ignored, nor does it successfully recaptcha in this regard.
But we can control them ...
It does not matter if a person uses bots or not, as long as they do not have an advantage over a person who does not use ... Limitations are necessary, so that the bots do not exceed the "humanly possible".
And so it will have equality, because if a person can follow a bot, there will be no advantage of the bot on the person.
"60 claims per minute? team or bot only!
only 1ip per claim/minute? only bots then"
Increase the top, will not solve, increase the difficulty of the captcha will not solve. The solution is in the backend. Validations and limitations need to be reviewed in the backend.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
Ways to improve the faucet:
(Backend)
Separate two "team" and "solo" interactions, with separate reward system.
solo:
Limit the number of clicks per minute to something humanly possible, through a database with timeout per wallet. (Recommended mongodb).
team:
Create an api paid via domain registration, with concurrent queries, through a database with timeout and consultation by ip and wallet. (Recommended mongodb).
(Frontend)
solo:
Decrease the difficulty of captcha and create a virtual keyboard with ids, organization and dynamically generated names functions to prevent scheduled execution.
team:
Through api, allow the site registered as a team to include the service through remote javascript (similar to recaptcha, solve media, facebook).
Rounds:
Whenever a round is finished, pause for 15 minutes while making the payments, and start a new round after all payments are completed. This would allow for greater system stability and auditing.
==============
This would allow ordinary people to continue to have a fair distribution, and sites like "claimers.io" continue to work with the raiblocks. In addition to decreasing and limiting the use of bots. Since they would not be able to bypass backend validations.
One way that would allow the community to contribute more would be to make available in github the fonts codes of the telegram bots(wallet and trade), this will allowed greater integration with other systems. The big mistake of the Raiblocks, is that it is very closed and its distribution monopolized by some people. This will greatly decrease the use of coin and your value.
Administrators need to stop complaining and ignore feedback about site of official distribution(faucet.raiblockscommunity.net), and facilitate integrations so that new uses are created for raiblocks, which today are only about 3 or 4 sites.
With access to the botwallet and tradebot codes, I think many would have new ideas for new systems.
In the source of the wallet, it is necessary to review some parts, which are generating errors. Like the "dumped core" problem generated by "blake2".
I intended to contribute with the system, but from the treatment received in the "slack group" when I mentioned the problems of the faucet, I give up contributing.
If the faucet is maintained by the official website, it is an official subject, and can not be ignored.
And while giving my feedback here, it's because I still have hopes in the currency. If you notice, all the criticisms made by me, it was pointed to serious distribution problems, which some are mocking. This weakens the economic stability of ecosystem of raiblocks.
*Adding that the botwallet is already available in github.
(Backend)
Separate two "team" and "solo" interactions, with separate reward system.
solo:
Limit the number of clicks per minute to something humanly possible, through a database with timeout per wallet. (Recommended mongodb).
team:
Create an api paid via domain registration, with concurrent queries, through a database with timeout and consultation by ip and wallet. (Recommended mongodb).
(Frontend)
solo:
Decrease the difficulty of captcha and create a virtual keyboard with ids, organization and dynamically generated names functions to prevent scheduled execution.
team:
Through api, allow the site registered as a team to include the service through remote javascript (similar to recaptcha, solve media, facebook).
Rounds:
Whenever a round is finished, pause for 15 minutes while making the payments, and start a new round after all payments are completed. This would allow for greater system stability and auditing.
==============
This would allow ordinary people to continue to have a fair distribution, and sites like "claimers.io" continue to work with the raiblocks. In addition to decreasing and limiting the use of bots. Since they would not be able to bypass backend validations.
One way that would allow the community to contribute more would be to make available in github the fonts codes of the telegram bots(wallet and trade), this will allowed greater integration with other systems. The big mistake of the Raiblocks, is that it is very closed and its distribution monopolized by some people. This will greatly decrease the use of coin and your value.
Administrators need to stop complaining and ignore feedback about site of official distribution(faucet.raiblockscommunity.net), and facilitate integrations so that new uses are created for raiblocks, which today are only about 3 or 4 sites.
With access to the botwallet and tradebot codes, I think many would have new ideas for new systems.
In the source of the wallet, it is necessary to review some parts, which are generating errors. Like the "dumped core" problem generated by "blake2".
I intended to contribute with the system, but from the treatment received in the "slack group" when I mentioned the problems of the faucet, I give up contributing.
If the faucet is maintained by the official website, it is an official subject, and can not be ignored.
And while giving my feedback here, it's because I still have hopes in the currency. If you notice, all the criticisms made by me, it was pointed to serious distribution problems, which some are mocking. This weakens the economic stability of ecosystem of raiblocks.
*Adding that the botwallet is already available in github.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
I need to comment something?
see rank... pure bots!
see rank... pure bots!
Quote
1 Funds for devs 109,364 8.43 1,433.884001
2 xrb_11sg9kxqtxm17f3qqs5kjabhzq8pb7jcjaidrw3w8fyt8471pwtowf1csu39 7,123 0.55 93.389901
3 xrb_1rdwtx77f8jcae6ju31h1o8dkbezmo6p7no9o1ej4e4srkq3rnd7qubb3mh9 7,122 0.55 93.376790
4 xrb_1qo7f4o4pp8xu95i7a4jshdjomndgmrswt6s5cnu16quth46xoho8bifo9fn 7,117 0.55 93.311235
5 xrb_154oyhohckw9cfro7wfj9of6cibxsawcc9xwqigz1m4i3ytqkgdwbm9qrq9o 7,105 0.55 93.153902
6 xrb_1t1igt7u7s4bf71fywcsjo3jafsnr6ig886cnu6hy3mcmci9hxdq386uagya 7,097 0.55 93.049014
7 xrb_1uizjam6o6xuc3mmpin1kz94nfudoy9hdb9g3kx7ksk5zhh3scybzze534qx 7,075 0.55 92.760571
8 xrb_148yja49r76x6dg7p578xjq4gkrg1z91h8k6n8n9fifibj9ax4qws6erfmt8 7,058 0.54 92.537684
9 xrb_19mqspidr3mrzitenzkdtct7dgyuzg9ozziaba9k64if9sotidyojmz3entr 7,057 0.54 92.524573
10 xrb_1yaubxapin1u3rqixsyas9w4es4dezrue3isoej5sjzpy7s8wsujz7dm4r6s 7,049 0.54 92.419684
11 xrb_14o1zwg5xtnf1g91sfj4yw396xoxqxdrw3341zkkhtxiu5mfxt74fjo396xr 7,043 0.54 92.341018
12 xrb_1czsai579kaqc6f7n6iiu8ybk9era4iue5soy7n44nbb71s1csrwr31x1n6o 7,043 0.54 92.341018
13 xrb_37jxjo4y9xnap963ytbgbxs6j7i8539yiducwoss47wjiwzn4cbe3r65s73o 7,039 0.54 92.288574
14 xrb_39qerqse9fm7eyjeshz6hsq7othgfoyyeyke63jbjpwuefyf4o365y7y1mun 7,035 0.54 92.236130
15 xrb_11p5ek8ndpk6na3sr95mw3gyfscywduxcwfn81du139mtajgasroem518tgw 7,007 0.54 91.869021
16 xrb_1iqide6krx54qjup67yb4r9wybor5scsnpgjjiq94u9qjn6uktoqho1y9a8t 7,001 0.54 91.799532
17 xrb_1oxwtr5jqpz95iqfmhh3mudse7kw45ezxom9c3fbzp18tmqmcizjejcmrdzn 6,965 0.54 91.318357
18 xrb_1p9otkf13pxttthso3p9ugd5u5zke46ywojpyhg38autuywq6bj169kxk1i1 6,943 0.54 91.029915
19 xrb_1nqpfwn4b7umw6bo3n8ke48on8wi6dz9nzepsui8iw3x4hsqg7ccrjong5p4 6,942 0.54 91.016804
20 xrb_1iz1i753spx7pu9goikunf56tsh83pwjcr7ny8499xfbj3cqbambxfzg9xz5 6,848 0.53 89.784366
21 xrb_15uau4dyfw4nojiuoqnpq8tztxj9dpgn1jgdmoi8doh15joy1ynp6p6fxcz6 6,837 0.53 89.640145
22 xrb_399yoost8k9hkc3j159omj9kucs1jrx99rg96esomhpfa4eai5apusjgae58 6,828 0.53 89.522146
23 xrb_1qjxmqxzbqgpxgxkazzbbi5fcgxsstwnitdntzyk17tciejah3t3d54rk9u5 6,812 0.53 89.312369
24 xrb_3cysmneboib3k38wa5onmes6kqb3xnbj1xg3iqa4hzqtf1brosej7kp35386 6,800 0.52 89.155037
25 xrb_1mb94gnidkiwzygwpmbxp5ebtbadhyc5ke7666gqdedca9ig8gu3mbp6ogmx 6,789 0.52 89.010815
26 xrb_36uo1oooprao7akrea4er86weo5kgb9591qnsbr5qe8ebwxfwwgqux61w6du 6,784 0.52 88.945260
27 xrb_33ur83zqmspch9au9ntwrsc9au4a87a151onncusu6hj6dgo7yxsb1wor8oc 6,774 0.52 88.814150
28 xrb_346jae7egs3hut687uizgpi4h1mkdp3dqgjdjyq16afoyajpxjz6obpmtkrr 6,769 0.52 88.748594
29 xrb_1g55ypacs4g1ogd13ojzn781w74zg9bzse4o6yiw3h8ybjf8nms4hfxz7ggh 6,762 0.52 88.656817
30 xrb_31s9d34nhouzm48k4t8ddt5b5irxzixfnqwkak4u3ya98pfj3z35j9imyhm3 6,758 0.52 88.604373
31 xrb_1zh5jgbajbqzpyzm9faxbmkwgtt6ipp3cbdmdaw8i7fdorp5z34ckf77g4u3 6,728 0.52 88.211042
32 xrb_1wqrngh4ceqkuj5mt84pbaeopnk1ywt17e3figkxyacbofokwu31o6yfqhte 6,560 0.51 86.008388
33 xrb_19fjrktqcdkrhhzg1ndi7quzhx9kg14occo8ryp5hkrfnyedcxomuzzg4a7n 6,395 0.49 83.845067
34 xrb_34y6j13i3uuhqu8yym3i1anuefujk9h3k5fh7wqby5ucxbtdp8q9d9w5s71z 6,384 0.49 83.700846
35 xrb_151n8n3feo93i9cjycx4y7myzrz6zhz1d743eamskp3q84o67s6e9o56fto5 6,343 0.49 83.163294
36 xrb_1itz4xtt6qnit6xupry8soe5nwzfduswriwqc8zox3xsktz9pm5175mttmx8 6,332 0.49 83.019072
37 xrb_1ak9bk4qyrrgr9hgntyxd5njwhc1k1k1rx1hxxnyb79c9p41uhisj49intyy 6,302 0.49 82.625741
38 xrb_3n8ymcn1o6ak858fs494fsu84keaxzd8amwjp1woutnmyhh3cjnkmi8ezi37 6,292 0.49 82.494631
39 xrb_3e1tmpfprbcqt3345u7tj35s4om6giimwrcn78zxnwc5ekxjm1wkwseik6h4 6,283 0.48 82.376632
40 xrb_1yuranmjzrmmfk9huex7zca8tdazccktuygm7ko9kpswwiggu1nbsxzinxnw 6,269 0.48 82.193077
41 xrb_17p1fj5pa9e845nyzurhgrxfswmi8t6cozriigek1tjdzax7furupdfncizq 6,259 0.48 82.061967
42 xrb_3aokg5gtiaujpb33tpmjrwsgjmmp97ucqdoopuer6rj97j1ar5hasadq4ma9 6,234 0.48 81.734191
43 xrb_15759ptgm1su8dr9cyebwxkd3cou71i5byxotn7pmmdp5nd1w5jmnfiion3f 6,209 0.48 81.407333
44 xrb_1t3yhiso5rspazz665zjtigfhdtsryne5fjzsa6kaphhh4e37qh4uyddqr55 6,192 0.48 81.195327
45 xrb_1ixo71twhdyxx485gkyimryecxzzcnpc83jwanomj7kh5ajjuxpf8fhw19rh 6,168 0.48 80.868863
46 xrb_3iiswnr8yjifcyaynrczrmgsxogdh94kq3kswq8aypukdr4tjheomus1zfjd 6,164 0.48 80.816418
47 xrb_397y9tunk66go748gta1g4tcfyd8zwakuniybwhmnzmspsz16sfoiz4skf1r 6,164 0.48 80.816418
48 xrb_1hz8bzzs1iibnuaz3tf9kjwi3xiksmm9n1sh4k5yte8kgsqy9p7j9faocsf8 6,144 0.47 80.554198
49 xrb_1d4pmp4a9jzmwqgaod8mj8u4yeqbas3g6a38cnwgxy5jqtgj5e8u1sheethh 6,129 0.47 80.357532
50 xrb_1hfmjsucd3qxuxciqmwcz7ygoimb5qm9xrnd1mu433gbhozffdqr8marjhk9 6,115 0.47 80.173978
2 xrb_11sg9kxqtxm17f3qqs5kjabhzq8pb7jcjaidrw3w8fyt8471pwtowf1csu39 7,123 0.55 93.389901
3 xrb_1rdwtx77f8jcae6ju31h1o8dkbezmo6p7no9o1ej4e4srkq3rnd7qubb3mh9 7,122 0.55 93.376790
4 xrb_1qo7f4o4pp8xu95i7a4jshdjomndgmrswt6s5cnu16quth46xoho8bifo9fn 7,117 0.55 93.311235
5 xrb_154oyhohckw9cfro7wfj9of6cibxsawcc9xwqigz1m4i3ytqkgdwbm9qrq9o 7,105 0.55 93.153902
6 xrb_1t1igt7u7s4bf71fywcsjo3jafsnr6ig886cnu6hy3mcmci9hxdq386uagya 7,097 0.55 93.049014
7 xrb_1uizjam6o6xuc3mmpin1kz94nfudoy9hdb9g3kx7ksk5zhh3scybzze534qx 7,075 0.55 92.760571
8 xrb_148yja49r76x6dg7p578xjq4gkrg1z91h8k6n8n9fifibj9ax4qws6erfmt8 7,058 0.54 92.537684
9 xrb_19mqspidr3mrzitenzkdtct7dgyuzg9ozziaba9k64if9sotidyojmz3entr 7,057 0.54 92.524573
10 xrb_1yaubxapin1u3rqixsyas9w4es4dezrue3isoej5sjzpy7s8wsujz7dm4r6s 7,049 0.54 92.419684
11 xrb_14o1zwg5xtnf1g91sfj4yw396xoxqxdrw3341zkkhtxiu5mfxt74fjo396xr 7,043 0.54 92.341018
12 xrb_1czsai579kaqc6f7n6iiu8ybk9era4iue5soy7n44nbb71s1csrwr31x1n6o 7,043 0.54 92.341018
13 xrb_37jxjo4y9xnap963ytbgbxs6j7i8539yiducwoss47wjiwzn4cbe3r65s73o 7,039 0.54 92.288574
14 xrb_39qerqse9fm7eyjeshz6hsq7othgfoyyeyke63jbjpwuefyf4o365y7y1mun 7,035 0.54 92.236130
15 xrb_11p5ek8ndpk6na3sr95mw3gyfscywduxcwfn81du139mtajgasroem518tgw 7,007 0.54 91.869021
16 xrb_1iqide6krx54qjup67yb4r9wybor5scsnpgjjiq94u9qjn6uktoqho1y9a8t 7,001 0.54 91.799532
17 xrb_1oxwtr5jqpz95iqfmhh3mudse7kw45ezxom9c3fbzp18tmqmcizjejcmrdzn 6,965 0.54 91.318357
18 xrb_1p9otkf13pxttthso3p9ugd5u5zke46ywojpyhg38autuywq6bj169kxk1i1 6,943 0.54 91.029915
19 xrb_1nqpfwn4b7umw6bo3n8ke48on8wi6dz9nzepsui8iw3x4hsqg7ccrjong5p4 6,942 0.54 91.016804
20 xrb_1iz1i753spx7pu9goikunf56tsh83pwjcr7ny8499xfbj3cqbambxfzg9xz5 6,848 0.53 89.784366
21 xrb_15uau4dyfw4nojiuoqnpq8tztxj9dpgn1jgdmoi8doh15joy1ynp6p6fxcz6 6,837 0.53 89.640145
22 xrb_399yoost8k9hkc3j159omj9kucs1jrx99rg96esomhpfa4eai5apusjgae58 6,828 0.53 89.522146
23 xrb_1qjxmqxzbqgpxgxkazzbbi5fcgxsstwnitdntzyk17tciejah3t3d54rk9u5 6,812 0.53 89.312369
24 xrb_3cysmneboib3k38wa5onmes6kqb3xnbj1xg3iqa4hzqtf1brosej7kp35386 6,800 0.52 89.155037
25 xrb_1mb94gnidkiwzygwpmbxp5ebtbadhyc5ke7666gqdedca9ig8gu3mbp6ogmx 6,789 0.52 89.010815
26 xrb_36uo1oooprao7akrea4er86weo5kgb9591qnsbr5qe8ebwxfwwgqux61w6du 6,784 0.52 88.945260
27 xrb_33ur83zqmspch9au9ntwrsc9au4a87a151onncusu6hj6dgo7yxsb1wor8oc 6,774 0.52 88.814150
28 xrb_346jae7egs3hut687uizgpi4h1mkdp3dqgjdjyq16afoyajpxjz6obpmtkrr 6,769 0.52 88.748594
29 xrb_1g55ypacs4g1ogd13ojzn781w74zg9bzse4o6yiw3h8ybjf8nms4hfxz7ggh 6,762 0.52 88.656817
30 xrb_31s9d34nhouzm48k4t8ddt5b5irxzixfnqwkak4u3ya98pfj3z35j9imyhm3 6,758 0.52 88.604373
31 xrb_1zh5jgbajbqzpyzm9faxbmkwgtt6ipp3cbdmdaw8i7fdorp5z34ckf77g4u3 6,728 0.52 88.211042
32 xrb_1wqrngh4ceqkuj5mt84pbaeopnk1ywt17e3figkxyacbofokwu31o6yfqhte 6,560 0.51 86.008388
33 xrb_19fjrktqcdkrhhzg1ndi7quzhx9kg14occo8ryp5hkrfnyedcxomuzzg4a7n 6,395 0.49 83.845067
34 xrb_34y6j13i3uuhqu8yym3i1anuefujk9h3k5fh7wqby5ucxbtdp8q9d9w5s71z 6,384 0.49 83.700846
35 xrb_151n8n3feo93i9cjycx4y7myzrz6zhz1d743eamskp3q84o67s6e9o56fto5 6,343 0.49 83.163294
36 xrb_1itz4xtt6qnit6xupry8soe5nwzfduswriwqc8zox3xsktz9pm5175mttmx8 6,332 0.49 83.019072
37 xrb_1ak9bk4qyrrgr9hgntyxd5njwhc1k1k1rx1hxxnyb79c9p41uhisj49intyy 6,302 0.49 82.625741
38 xrb_3n8ymcn1o6ak858fs494fsu84keaxzd8amwjp1woutnmyhh3cjnkmi8ezi37 6,292 0.49 82.494631
39 xrb_3e1tmpfprbcqt3345u7tj35s4om6giimwrcn78zxnwc5ekxjm1wkwseik6h4 6,283 0.48 82.376632
40 xrb_1yuranmjzrmmfk9huex7zca8tdazccktuygm7ko9kpswwiggu1nbsxzinxnw 6,269 0.48 82.193077
41 xrb_17p1fj5pa9e845nyzurhgrxfswmi8t6cozriigek1tjdzax7furupdfncizq 6,259 0.48 82.061967
42 xrb_3aokg5gtiaujpb33tpmjrwsgjmmp97ucqdoopuer6rj97j1ar5hasadq4ma9 6,234 0.48 81.734191
43 xrb_15759ptgm1su8dr9cyebwxkd3cou71i5byxotn7pmmdp5nd1w5jmnfiion3f 6,209 0.48 81.407333
44 xrb_1t3yhiso5rspazz665zjtigfhdtsryne5fjzsa6kaphhh4e37qh4uyddqr55 6,192 0.48 81.195327
45 xrb_1ixo71twhdyxx485gkyimryecxzzcnpc83jwanomj7kh5ajjuxpf8fhw19rh 6,168 0.48 80.868863
46 xrb_3iiswnr8yjifcyaynrczrmgsxogdh94kq3kswq8aypukdr4tjheomus1zfjd 6,164 0.48 80.816418
47 xrb_397y9tunk66go748gta1g4tcfyd8zwakuniybwhmnzmspsz16sfoiz4skf1r 6,164 0.48 80.816418
48 xrb_1hz8bzzs1iibnuaz3tf9kjwi3xiksmm9n1sh4k5yte8kgsqy9p7j9faocsf8 6,144 0.47 80.554198
49 xrb_1d4pmp4a9jzmwqgaod8mj8u4yeqbas3g6a38cnwgxy5jqtgj5e8u1sheethh 6,129 0.47 80.357532
50 xrb_1hfmjsucd3qxuxciqmwcz7ygoimb5qm9xrnd1mu433gbhozffdqr8marjhk9 6,115 0.47 80.173978
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
"Houston read the wiki"
Claims limit now is 60.
Between captcha load, post and post reply, you already lose 1 second!
If 60 seconds = 1 minute, and you lose 1 second with load/reload of captcha, how many captcha can you generate in 1 minute?
Simple math!
The captcha limit per minute is 30! Regardless of whether the wiki says 120, you will not be able to do more than 30, even if you get the miracle of responding 30 alphanumerical and distorted captcha on miliseconds, the system will not respond to you at the same time.
I am not against use of automation systems.
The problem is that these people who are using, are abusing the faucet.
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
I dont get what you trying to explain here. You wont get the claims every hour unless you are in the top claimed addresses for that hour. However,if you are not paid for an hour your previous claims will add to the unpaid and you will be paid once you're in the top addresses.
@jennywhzz,
If to enter the top 200 needs the minimum of "3,562" this means that the person in the top, started with that amount or less.
correct?
So there is no way she could start the round with more than the minimum, otherwise she would have been paid in the last round, and would have zeroed in the claims.
Now let's calculate using the +0.05
If the limit is 30 claims per min, the round lasts 60min, the maximum claims is 1890 per hour, using the limit of 30 claims per min. You can not have more than that this value. right?
1.05*30 = 31,5 claims per min(max).
31,5*60 = 1890 claims per hour(max with bonus +0.05).
1890(max claims per hour) + 3562(min for top 200) = 5452(max claims for top 1).
So how is it possible for the top 1 to get that value in less than an hour?
xrb_1p569kkuhz4r659x94i35a8ctruftb8bp4qmyutwyg9wwmkymkgaywct6bum 6,336 0.81 138.511952
And several ips with the same account are no longer allowed
It is humanly impossible for a single person to reach this value without bot
Is beyond the limit of 30 claims per min! How I told
Captchas, bots will always adapt to the captchas, has websites expert in selling such services.
The problem lies in limiting claims by min or hour!
The difficulty of captcha only delay people who do not use bots, and leave the system only for bots ...
Which ultimately results in what happens in a hardware mining!
Who can afford an automated service concentrates the highest profit.
"Houston we have a problem!"
Because a system fault is evident!
Re: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments
Increased the difficulty of captcha and apparently only "I" stayed slower.
Before ... 800 claims per hour!
now half only!
Captchas dificies + currency falling = time lost
It is not in captcha that you managed to stop the abusers, but within the limits of claims per hour ... will it be so difficult to differentiate a bot / team from a person by the amount made? Just think what is humanly possible
I even considered it fun to make captchas, now it's a real boredom ...
And think about losing more than 3 hours of my time, to win only 1400dogers. Can be discouraging.
Before ... 800 claims per hour!
now half only!
Captchas dificies + currency falling = time lost
It is not in captcha that you managed to stop the abusers, but within the limits of claims per hour ... will it be so difficult to differentiate a bot / team from a person by the amount made? Just think what is humanly possible
I even considered it fun to make captchas, now it's a real boredom ...
And think about losing more than 3 hours of my time, to win only 1400dogers. Can be discouraging.