Author

Topic: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments - page 342. (Read 775150 times)

hero member
Activity: 1638
Merit: 756
Bobby Fischer was right
Quote
-----------------IMPORTANT ANNOUNCEMENT------------

We are starting our new marketing campaign.......

Crypto Alliance is a team of motivated professionals that have experience managing and directing organized trading calls, as well as organized fair pumps. We currently are ran by a team of five owners,which consist of a web/app developer, public relations manager, market analysts, pump organizer, and an experienced investor, all of which offer constant support to our users . We work as an alliance to ensure that our team is both well informed on modern events, as well as finding profitable coins to push large sums of volume. We currently operate out of our slack team, which consists of two separate tiers premium and free; the premium tier gets personalized market signals and access to long term pumps, with a unique method exclusive to our team to ensure profitability for all within our premium team. We also offer quick pumps for our general users which are free to the public. Free users will not receive as much support from the community, but if they find success with us we encourage our general users to join our premium group sooner than later, as we are limiting our premium team to dedicated users only with a cap to how many users will be able to join premium.
Just received this email from raiblocks slack group.
No one posted it here yet so I think it could come in handy for people without slack account.
What really strikes me here is the fact that devs and their communication channel are turning in to pump/dump group. It starts to look like milking a ding cow now. No further ideas for coin development so at least turn the traffic and "fame" in to some cash from premium subscriptions... It is of course entirely theirs project and devs are free to do anything they want with it but, seriously? premium pump&dump? How on earth this approach will help Raiblocks? Devs pockets maybe, but not the coin.
Glad to see new active representative tho Smiley jayycox
Maybe this news quoted above is just fake or hoax, could you make a statement about it?
hero member
Activity: 1792
Merit: 536
Leading Crypto Sports Betting & Casino Platform
Technical Analysis of a Feature
What Does ‘Not Pocketed’ Mean?
This means that the destination wallet hasn’t yet received the send block - this is nearly always as this wallet is not completely synced up. A XRB transaction consists of 2 blocks, a send block from the sending wallet and a receive block from the receiving wallet - both need to be fully synced for the transaction to go ahead.
Therefore if you have sent XRB and it isn’t pocketed then you just need to wait for the destination wallet to sync, do not worry - your XRB aren’t lost.


>>> then why is my transaction since june still not pocketed until now?
https://raiblockscommunity.net/block/index.php?h=917387A82BF80273200EA3D949D1A22107683F23CF6066E592A2507E44EDED86
member
Activity: 98
Merit: 10
yesterday 500 claim/s today 270 claim/s cheating die LOL
newbie
Activity: 41
Merit: 0
Great replies from jamilservicos

You are completely right - you have to understand the issue before you can solve it and that its not just a matter of increasing captcha difficulty. I can assure you that a lot of work goes on where we identify how people are trying to cheat the system and then implement changes to the backend validation to try and stop it - like all security its a constant battle to catch up with changes. A lot of your ideas are already implemented or being implemented to be honest.

Looking forward to seeing your progress on developing your idea for the faucet, perhaps a white paper or even a proof of concept, your proposed system would be a shift away from the current setup so probably needs to be thought of separately. As I said before I will be happy to review your work at a future date, Good luck!
newbie
Activity: 27
Merit: 0
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.
legendary
Activity: 1694
Merit: 1003
difficulty in claiming and bugs are all part of it, most of the program have it, and maybe they are trying to make the system secure many hack are happening right now and the main target is ETH. 
legendary
Activity: 3346
Merit: 1214
claim wrong -1 claim?

That seems to be a new rule. I'm not seeing it on the wiki though. I guess that new rule (if it really is) is for dealing with bots. Usually, bots' invalid claims are more than valid claims, and that new rule makes bots get no claim in the end.

I think they're testing or implementing new ways to make it difficult to claim in the faucet or to minimize abuse. I'm looking forward for a better wallet though instead of the faucet.

I stop claiming because of so many bugs and the difficulty of claiming, this is because mrai has become so popular they need to upgrade everything, like what you are hoping, I'm hoping that wallet and faucets will be upgraded too to a point where everybody can claim fairly.
sr. member
Activity: 714
Merit: 252
claim wrong -1 claim?

That seems to be a new rule. I'm not seeing it on the wiki though. I guess that new rule (if it really is) is for dealing with bots. Usually, bots' invalid claims are more than valid claims, and that new rule makes bots get no claim in the end.

I think they're testing or implementing new ways to make it difficult to claim in the faucet or to minimize abuse. I'm looking forward for a better wallet though instead of the faucet.
newbie
Activity: 27
Merit: 0
@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!


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.
newbie
Activity: 41
Merit: 0
DISCLAIMER - I do not run the faucet. I however do run YapRai Wallet and the raiblockstradebot and am part of the dev team for raiblocks. I'm taking a risk by replying only because I'm hoping to be more responsive on BCT - therefore would appreciate sensible replies. Also please don't take my reply as negative or patronising - its meant to be encouraging.


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.


The faucet is hard, really hard, there have been loads of suggestions on how to improve it, thousands are 'dev decrease TH' or 'increase top 200' and then any changes are met with backlash of 'now i don't get as much' or its too slow or the pools are stealing my xrb and if it gets particularly nasty then there is a lot of rascism which is just not acceptable. This got to a point where it was impossible to actually discuss raiblocks without being flooded with this - The team had to move off telegram onto slack and then from there still struggle with more and more complaints.

I really appreciate you taking the time to write a proposal on how to improve the faucet and I've posted it onto the admin channel for review. Why not develop your idea further, perhaps a white paper or even demo set up - I promise that I'll take it seriously but can't guarantee that it will be implemented.
There are members of the dev team who put hours a day into trying to maintain the faucet, lots of behind the scenes work has been done and they are constantly working - even today they have implemented methods to try and fight the issues of bots.

Quote
With access to the botwallet and tradebot codes, I think many would have new ideas for new systems.

In regards to the the source code of various programs that use raiblocks there are loads of open source examples out there. I have been cautious releasing the tradebot source code due to concerns about exploits - you could have always contacted me directly to ask for advice or to see the code. I've published 4 rai projects on github already (https://github.com/jamescoxon?tab=repositories) and developed an open web api to interface with yaprai wallet, there is a #development channel on slack and for the api for yaprai go to #yaprai_api.

Quote
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".

Finally the wallet development is ongoing - the lead dev is working really hard on it, as per the newsletter 17 commits in 14 days and it had been noted in the last few days that there was an IO issue which he has already developed a fix for and they recently 'recruited' a new dev to start work on fixing some of the bugs.

Quote
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.
The best way to get involved in raiblocks is by doing something, write code, design a logo, make something - actions speak louder then words
newbie
Activity: 27
Merit: 0
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.
full member
Activity: 280
Merit: 100
claim wrong -1 claim?

That seems to be a new rule. I'm not seeing it on the wiki though. I guess that new rule (if it really is) is for dealing with bots. Usually, bots' invalid claims are more than valid claims, and that new rule makes bots get no claim in the end.
member
Activity: 98
Merit: 10
WTF refresh image -1 claim?
member
Activity: 98
Merit: 10
claim wrong -1 claim?
newbie
Activity: 11
Merit: 0
RaiBlocks Newsletter 23rd July 2017

Introduction
This will hopefully be a short newsletter published every 2 weeks with info and updates in regards to RaiBlocks including core development and third party development. If you would like to get involved please get in contact (see details at the end).

Core Wallet/Node Development
In last 14 days there have been 17 commits including some GUI changes as well as changes to the core to improve optimisation and improve syncing nodes. This is good progress towards a new release. - https://github.com/clemahieu/raiblocks/commits/master
@vraken has joined the core dev team - he plans to start with some small bugs and go from there.

Beginning of 3rd party games
The last few weeks there has been lots of development of 3rd party games - RaiBlocks is ideal for games due to its near instant transactions and no fee. If you would like to develop or integrate RaiBlocks into a project you can either run your own node and use the RPC (good for a big project) or you could use the web api for the YapRai wallet - for more information check out #development and #yaprai_api on the slack channel.
Check out these games - remember that some involve gambling so stay safe!

XRB Jump and Grab - http://stats.yapraiwallet.space/games/arcade/start.html
RaiGames.io (Social RaiBlocks Gaming) - https://raigames.io/
BlockFevr (Provably fair dice game for RaiBlocks) - https://blockfevr.com/game/dice/XRB

Interview of RaiBlocks User
Helmi M (@MatheLZard on telegram)

1)How did you find out about RaiBlocks?
I know RaiBlocks since February, i found RaiBlocks when i read it in bitcointalk forums.

2)How have you used RaiBlocks?
I think RaiBlocks have a good cryptocurrency coin because having a very active community. Therefore I made RaiBlocks my investment cryptocurrency.

3)Where is RaiBlocks going to be in 6 months?
RaiBlocks will be in the big marketplace, because gradually many Investors have been eyeing RaiBlocks as a place to invest very well in the field of cryptocurrency.

Technical Analysis of a Feature
What Does ‘Not Pocketed’ Mean?
This means that the destination wallet hasn’t yet received the send block - this is nearly always as this wallet is not completely synced up. A XRB transaction consists of 2 blocks, a send block from the sending wallet and a receive block from the receiving wallet - both need to be fully synced for the transaction to go ahead.
Therefore if you have sent XRB and it isn’t pocketed then you just need to wait for the destination wallet to sync, do not worry - your XRB aren’t lost.

Dev Profile
SergSW (@SergSW on telegram or @sergsw on slack)

1)What Projects Do You Work On?
RaiWalletBot, RaiBlocksJS, RPC extensions

2)What makes RaiBlocks easier to use then other crypto?
Note: ideal future situation. People shouldn’t care about high commissions and 1 hour confirmation delays, RaiBlocks usage will be as easy as cash. If you buy 10 USD pizza, 1.5 USD commission is too expensive. You can remember some good crypto with relatively low commissions like DogeCoin, but imagine Doge with 100 TX/second & commission will be expensive again. Without commissions RaiBlocks can be used by anyone.

3)Whats the main challenge for RaiWalletBot?
For RaiWalletBot is was "How to handle several thousands incoming transaction in 1-2 hours?" :joy: (By using OpenCL and a dedicated GPU instead of CPU work).

4)Where is RaiBlocks going to be in 6 months?
In the middle of distribution :wink: Actually users will acknowledge XRB usefulness with more services to come


Feedback is welcome regarding the newsletter, you can contact me @jayycox on slack or telegram. It would be great if people wanted to review some of the services e.g. the new games.

Great to see initiatives like that. We definitely need more people genuinely interested in the coin itself not only the faucet part!
newbie
Activity: 3
Merit: 0
member
Activity: 98
Merit: 10
When will you be satisfied?
Your life isn't all about faucet.
Hope your life will be full of happiness.
when cheat die
sr. member
Activity: 742
Merit: 251
When will you be satisfied?
Your life isn't all about faucet.
Hope your life will be full of happiness.
newbie
Activity: 27
Merit: 0
I need to comment something?

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
newbie
Activity: 46
Merit: 0
RaiBlocks Newsletter 23rd July 2017

Introduction
This will hopefully be a short newsletter published every 2 weeks with info and updates in regards to RaiBlocks including core development and third party development. If you would like to get involved please get in contact (see details at the end).

Core Wallet/Node Development
In last 14 days there have been 17 commits including some GUI changes as well as changes to the core to improve optimisation and improve syncing nodes. This is good progress towards a new release. - https://github.com/clemahieu/raiblocks/commits/master
@vraken has joined the core dev team - he plans to start with some small bugs and go from there.

Beginning of 3rd party games
The last few weeks there has been lots of development of 3rd party games - RaiBlocks is ideal for games due to its near instant transactions and no fee. If you would like to develop or integrate RaiBlocks into a project you can either run your own node and use the RPC (good for a big project) or you could use the web api for the YapRai wallet - for more information check out #development and #yaprai_api on the slack channel.
Check out these games - remember that some involve gambling so stay safe!

XRB Jump and Grab - http://stats.yapraiwallet.space/games/arcade/start.html
RaiGames.io (Social RaiBlocks Gaming) - https://raigames.io/
BlockFevr (Provably fair dice game for RaiBlocks) - https://blockfevr.com/game/dice/XRB

Interview of RaiBlocks User
Helmi M (@MatheLZard on telegram)

1)How did you find out about RaiBlocks?
I know RaiBlocks since February, i found RaiBlocks when i read it in bitcointalk forums.

2)How have you used RaiBlocks?
I think RaiBlocks have a good cryptocurrency coin because having a very active community. Therefore I made RaiBlocks my investment cryptocurrency.

3)Where is RaiBlocks going to be in 6 months?
RaiBlocks will be in the big marketplace, because gradually many Investors have been eyeing RaiBlocks as a place to invest very well in the field of cryptocurrency.

Technical Analysis of a Feature
What Does ‘Not Pocketed’ Mean?
This means that the destination wallet hasn’t yet received the send block - this is nearly always as this wallet is not completely synced up. A XRB transaction consists of 2 blocks, a send block from the sending wallet and a receive block from the receiving wallet - both need to be fully synced for the transaction to go ahead.
Therefore if you have sent XRB and it isn’t pocketed then you just need to wait for the destination wallet to sync, do not worry - your XRB aren’t lost.

Dev Profile
SergSW (@SergSW on telegram or @sergsw on slack)

1)What Projects Do You Work On?
RaiWalletBot, RaiBlocksJS, RPC extensions

2)What makes RaiBlocks easier to use then other crypto?
Note: ideal future situation. People shouldn’t care about high commissions and 1 hour confirmation delays, RaiBlocks usage will be as easy as cash. If you buy 10 USD pizza, 1.5 USD commission is too expensive. You can remember some good crypto with relatively low commissions like DogeCoin, but imagine Doge with 100 TX/second & commission will be expensive again. Without commissions RaiBlocks can be used by anyone.

3)Whats the main challenge for RaiWalletBot?
For RaiWalletBot is was "How to handle several thousands incoming transaction in 1-2 hours?" :joy: (By using OpenCL and a dedicated GPU instead of CPU work).

4)Where is RaiBlocks going to be in 6 months?
In the middle of distribution :wink: Actually users will acknowledge XRB usefulness with more services to come


Feedback is welcome regarding the newsletter, you can contact me @jayycox on slack or telegram. It would be great if people wanted to review some of the services e.g. the new games.

Good news from Raiblocks..
I hope will boost and pump the price
Jump to: