Search the Community
Showing results for tags 'server'.
Found 5 results
Minimum search term is 4 characters long. Can't find what you want? Click here for the custom google search instead.
-
Hey guys, I'm an Ethereum developer and I'm new here so if this question should be posted somewhere else I apogize in advance. So I studied the first ripple whitepaper(not the one published in 2018), "The Ripple Protocol Consensus Algorithm", and wanted to ask some questions(any help would be greatly appreciated): 1) firstly, what is the difference between a node and a server in Ripple? According to the whitepaper "any entinty running the Ripple Server Software is a server". I get this. We have stock servers and validator-servers? Is it the same if I call a server, a node. Intuitively I feel like running a stock-server in Ripple is kind of the same as running a GETH node in eth, right? This may sound simple but I want to know what is what. 2) is there an option for end users to run a UNL? Is the validator-server a UNL? If yes, I can answer the first part(yes). Since you can decide to run a validator server you can run a UNL. 3) the basic idea is that we split the network into subnetworks - UNLs and we verify these UNLs so in the end we combine these and verify the whole system. This is great but isn't it less secure than having a ethereum-like system where every node validates every transaction? 4) what is the latency requirment to participate in the voting process. Apart from the 2 second window for the candidate set submission. I mean is there any other requirement? 5) finally i felt strange with the fact that there is a flag/kick system for nodes in the network combined with the fact that the code isn't open source. Thank you in advance if you took the time to read my questions
-
I am new to rippled and am trying to learn what the difference is between a stock rippled node and a validating node. As I've read, a Stock server follows the network with a local copy of the ledger whereas a Validating server participates in consensus (and does everything a stock server does, too). I am currently running an instance of rippled and have run a performance profiler on the node, first on the non-validating node and then again when the node is running as a validator. Looking through the results, it seems that even when not running as a validator, the server makes calls to functions associated with consensus (ripple::RCLConsensus::Adaptor::doAccept, ripple::RCLConsensus::Adaptor::buildLCL, etc.) If a stock server is not supposed to be participating in consensus, why would there be calls to these functions? Could anyone explain to me why this is?
-
This article mentions some issues with Ripple's servers. https://medium.com/@slinafirinne/on-december-29th-lots-of-coins-went-missing-on-the-xrp-ripple-network-a1655e8d636d Could this be the problem that plague's exchanges and be the reason why people can't get their coins off of exchanges sometimes? This is far beyond me technically, but I think it's worth looking at and addressing for future and current XRP holders, as well as any technical experts that may be able to shed light on the potential issue. @nikb @JoelKatz @Sukrim -
Which type of AWS instance is suitable for rippled (only home research purpose) - getting mixed opinions: 1. t2.2xlarge (Variable ECUs, 8 vCPUs, 2.4 GHz, Intel Xeon Family, 32 GiB memory, EBS only) 2. m4.2xlarge (26 ECUs, 8 vCPUs, 2.4 GHz, Intel Xeon E5-2676v3, 32 GiB memory, EBS only) 3. m3.large (6.5 ECUs, 2 vCPUs, 2.5 GHz, Intel Xeon E5-2670v2, 7.5 GiB memory, 1 x 32 GiB Storage Capacity) 4. g2.2xlarge (26 ECUs, 8 vCPUs, 2.6 GHz, Intel Xeon E5-2670, 15 GiB memory, 1 x 60 GiB Storage Capacity) Thanks folks.
-
I've never worked with servers, but one can't help to have noticed that there seems to be an endless variety of ways to hack them. With the growth of crypto-currencies, it seems like the current generation of server operating systems/applications is woefully outdated. Why is this? Is a new generation of architecture needed to provide the security that is required? Does anyone know if this is something that is being worked on, or are our so-called guardians of the internet and operating systems developers going to keep adding more plugs, band-aids, pieces of tape, and rubber bands to what already exists?
