|
Hey everyone, RaiBlocksCommunityWill has been building tools and setting up a faucet for us to use so make sure to thank him.
I'm working on core node stability and features and we're keeping an eye out for anything indicative of the rollback issue which hasn't recurred.
As with any computer programs, confidence comes with time and eyes-on-code so please keep in mind the youngness of this code.
|
|
|
|
Thanks for the feedback guys. One thing I'd like people to think about is concentration on the faucet versus concentration on using the system. If you like the technical aspects of the system, no transaction fees and speed, attention due to the faucet isn't a long term sustainable solution.
The only thing that sustains the system long term is developing bona-fide usefulness. When people want to use the system because it solves their issues better and more cheaply than the alternatives, that's what'll make everything work long term.
how about closing faucet i think its causing more problems current amount of coins is ok The point of continuing the faucet is so early discoverers aren't overly favored. You're right though, even the current amount of xrb out there would be enough to probably last forever without needing something like a split. |
|
|
|
|
Thanks for the feedback guys. One thing I'd like people to think about is concentration on the faucet versus concentration on using the system. If you like the technical aspects of the system, no transaction fees and speed, attention due to the faucet isn't a long term sustainable solution.
The only thing that sustains the system long term is developing bona-fide usefulness. When people want to use the system because it solves their issues better and more cheaply than the alternatives, that's what'll make everything work long term.
|
|
|
|
|
The status is the same. The network is running, we're inspecting logs to identify issues since 7.5.0 but haven't found any. The faucet if off while we're working on its scalability after which we'll turn it on.
The faucet is unnecessary for normal network operation and these questions are usually the same one, when will it be up, and the answer is when we finish.
I don't post updates as often here because this is a Bitcoin forum, please post on the RaiBlocks forum or a message in telegram for specific issues.
|
|
|
|
|
The faucet maintenance wasn't completed. We're working on getting it running as soon as possible.
|
|
|
|
Yeah, that is perfect. Thanks! I don't promise to have it online right away, but maybe in a few days when i have looked into it a bit deeper. Cheers, Novaexchange Let me know if I can help at all, I'm the developer of RaiBlocks. I'm in Telegram chat https://telegram.me/raiblocks and I'll mark this thread as watching. |
|
|
|
|
Yes, please let exchanges know you want RaiBlocks listed.
I've talked with Bittrex, Poloniex, C-Cex, many, many others over a period of almost 9 months trying to get accepted.
I doubt many are more irritated at the situation than I am, if *any* of them would contact me back I'd be helping them get it listed.
|
|
|
|
My guess is that people who hold large Mrai balances will want to run a node, otherwise their holding will devalue.
What is system requirements to run RAI node? Wallet is CPU incentive. Is VPS enough or you need something like dedicated 16-core Xeons? Also the transaction rate grows... The CPU usage is put on to transaction generators. Being a representative is extremely light. The representative nodes I run are on 1 core 4$/mo vps machines. The goal is to make running a representative as cheap as possible so we can get a greater diversity and decentralization. |
|
|
|
How is the RAI blockchain secured without incentives for securing it? What about if only 10 people open up their wallets daily? I don't get how captchas will replace the pow/pos security
Bitcoin doesn't exactly have incentives for running a full node either. Miners could just mine blocks without processing any transactions. So the fees paid to the miners are not incentives? whaaaaa??? Yes, but RaiBlocks doesn't need miners. I don't think a lot of people understand how RaiBlocks works, dev should put up a simple explanation on how everything is secured and how it compares in tech with other cryptos. Does this help? https://docs.google.com/document/d/13s6BKzRq9oD5Me55JBRzR7BdvjJ44QKqPu2lf-JsAlU/edit |
|
|
|
The account_balance and send RPCs are heavily used by the faucet. We have some conversion functions for mrai/krai/rai to and from but I agree, we probably want to minimize that because it's confusing.
In the next release I'm going to make it selectable and probably default on krai.
I saw your solid background on Linkedin. May I ask. are you working full time on this project? I bet not. then what is your plan or vision for Raiblock? one thing is impressive is that You have developed it for 2 years. The rough timeline I see on RaiBlocks is like this: - Teach and encourage decentralization by having people set up representative nodes - Complete the initial distribution so the network has its final supply - Finish up features like multicast transactions and ledger checkpoints to reduce data usage At that point I think RaiBlocks itself will be in maintenance mode with the standard being managed something like an internet RFC. The base layer will have been established and hopefully will require infrequent changes. |
|
|
|
For the exchange - I would say we could do a campaign for Poloniex, it is by far the best alt exchange out there. However I'm hesitant in submitting a proposal to Polo, because I think the devs should provide clear instructions on how to run a node that can be used for exchanges. i.e. they should provide clear instructions on how to run the API, balance transfers, etc. I've played with the RPC and while it is workable, there is more to want, and I personally would not be comfortable running an exchange with what the RPC API has to offer. What I would like to see is: - Clear instructions on setting up a secure node using docker - this is almost there. But may need section on how to automatically update, etc.
- Clear instructions on how to do RPC commands that an exchange would need - most exchanges prefer format similar to Bitcoin, even if the cryptos are very different from BTC
- Create account RPC didn't seem to work for me at all - that's something that will need to be automated
- Alternatively - if import from private key works, then exchanges could use that
- Check account balance - this is working for me, but should have examples
- Send transaction - haven't tested that via RPC, but I'm assuming it works
In general - some scripts should be included in the code base that deal with certain operations as an example. The RPC is always using the smallest rai unit, correct? Even if the GUI is showing Mrai/krai/etc. I worry that as the devs allow the smaller units - it will confuse a lot of people. These are good suggestions, especially the example scripts. I'll finish up the docker node documentation especially around backing up and restoring the wallet seed which would be highly important to exchanges. The other thing I finished up recently is simplifying the build process for people that want to build it themselves. The account_balance and send RPCs are heavily used by the faucet. We have some conversion functions for mrai/krai/rai to and from but I agree, we probably want to minimize that because it's confusing. In the next release I'm going to make it selectable and probably default on krai. |
|
|
|
is paying less Mrai now also when can you have stats on how much an amount been copleted, stats?
It's paying the same, 21,000 per hour. |
|
|
|
Meh maybe I can recover some files that were deleted by sandboxie with Recuva or some program, last chance ..
EDIT : I've found data.ldb file that was last modified today at 18:43, dunno if this might help me somehow
All the data is stored there so it should be a drop-in replacement to recover what's in there. Alright but what do I do with that data file? Also I found the backup file that was last modified today at 18:43 and I've imported the file and wallet became unresponsive and now it wont even open again .. May I have ur skype or something, I don't want to spamm this thread with my problems. We're on telegram chat, that'd probably be the easiest. https://telegram.me/raiblocks |
|
|
|
Meh maybe I can recover some files that were deleted by sandboxie with Recuva or some program, last chance ..
EDIT : I've found data.ldb file that was last modified today at 18:43, dunno if this might help me somehow
All the data is stored there so it should be a drop-in replacement to recover what's in there. |
|
|
|
How to compete spam without fees?
A small hashcash style proof of work. |
|
|
|
Yea that sound like a suspect, the PoW that's used to prevent transaction spam. Are you running it inside a VM? Possible 1 CPU core? In your config.json what does it list for work_thread and io_thread count?
The PoW in the transaction makes sense, but I'm not sure why it's needed at address generation time. By the way - trying to create addresses via the RPC does not appear to be functional. (Something an exchange will likely need) Got 8 threads - again it's not that long of a time it's down. It's workable. But I imagine an exchange would need to handle at least 100 times more transactions. What you're noticing is precaching the PoW for your next transaction. I designed the PoW so it uses information from your previous transaction so in the usual case you can fire off 1 transaction instantly and the work generation latency gets hidden in the time until your next transaction. Part of this will be helped with the OpenCL module I'm putting together for people who need to handle higher transaction loads. |
|
|
|
Interesting. Thinking about it I suspect the GUI may not handle that many addresses that well though of course an exchange would use a headless node.
Do you notice slowness during any particular action?
Nothing that is unworkable. But here are a few notes: - Slowness happens when generating the addresses, and CPU usage goes up / fans start up, etc. - Slowness also occurs when it is the end of the 2 hours distribution period and balances are being processed - During that "processing" period (probably in another thread) I also get unresponsiveness, such as: - transfers go on hold until processing is done - RPC commands are just blocked until processing is done - quitting the GUI just "hangs" until processing is done I'm just thinking if I was an exchange, I'd need a receive address per account, so I'd have to have them pre-generated, or generate on the fly. Either way, it seems generating an address requires some CPU power by itself. (Does it have some PoW associated with it, to prevent address spam?) Yea that sound like a suspect, the PoW that's used to prevent transaction spam. Are you running it inside a VM? Possible 1 CPU core? In your config.json what does it list for work_thread and io_thread count? |
|
|
|
I'm working on cleaning up the build process this weekend, we have a semi lead that I'll be trying to make happen as much as I can. I know a trade thread is an awkward way to do this so I know everyone wants it to happen.
Excellent! I would say put clear instructions and documentations on how to deal with the RPC stuff. Also might be useful to provide some simple cli scripts. Exchanges would need to be able to receive to >100,000 addresses and client should not collapse. I know with just 700 addresses my client is chugging and slow. Just my 2 rai. Interesting. Thinking about it I suspect the GUI may not handle that many addresses that well though of course an exchange would use a headless node. Do you notice slowness during any particular action? |
|
|
|
|
I'm working on cleaning up the build process this weekend, we have a semi lead that I'll be trying to make happen as much as I can. I know a trade thread is an awkward way to do this so I know everyone wants it to happen.
|
|
|
|
|
Show Posts
