|
Skyzer0
Newbie
Offline
Activity: 266
Merit: 0
|
|
July 28, 2018, 06:44:28 AM |
|
Was just about to post this, good work guys.
|
|
|
|
|
codesdnc
Newbie
Offline
Activity: 23
Merit: 0
|
|
July 29, 2018, 11:02:54 PM |
|
Block time is only designed to average every 10 minutes. If difficulty spikes, a few blocks will be quicker. As difficulty drops, a few blocks will be longer. That's just the lag inherent in the difficulty calculation, to keep wild swings in check. At present, it's trending upward, with some noticeable dips along the way -- so some block times will be greater than 10 minutes, and some less than.
|
|
|
|
xr5248
Newbie
Offline
Activity: 17
Merit: 0
|
|
July 30, 2018, 07:37:05 AM |
|
Block time is only designed to average every 10 minutes.
Block time is designed to average 240 seconds or 4 minutes, not 10 minutes.
|
|
|
|
codesdnc
Newbie
Offline
Activity: 23
Merit: 0
|
|
July 30, 2018, 05:20:45 PM |
|
Block time is only designed to average every 10 minutes.
Block time is designed to average 240 seconds or 4 minutes, not 10 minutes. Apologies -- you are correct, it is idealized to 4 minutes. The rest of my logic still holds, however. I do remember a few block times of around an hour due to difficulty spikes back when original Sumo was still on CN -- ASICs would join, snap up some blocks, then leave. This lead to the difficulty spiking, and with the now-reduced hasrate, it took a long time for the rest of the network to find the next 1-2 blocks (at which point the difficulty would correct). This "situation" lead to the fork to CN-Heavy. +10 minutes, tho not ideal, isn't near as bad as +60 minutes.
|
|
|
|
Nostradamus411
Copper Member
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 30, 2018, 06:00:31 PM |
|
Block time is only designed to average every 10 minutes.
Block time is designed to average 240 seconds or 4 minutes, not 10 minutes. Apologies -- you are correct, it is idealized to 4 minutes. The rest of my logic still holds, however. I do remember a few block times of around an hour due to difficulty spikes back when original Sumo was still on CN -- ASICs would join, snap up some blocks, then leave. This lead to the difficulty spiking, and with the now-reduced hasrate, it took a long time for the rest of the network to find the next 1-2 blocks (at which point the difficulty would correct). This "situation" lead to the fork to CN-Heavy. +10 minutes, tho not ideal, isn't near as bad as +60 minutes. You're on the right track, the fork from CN to CN-Heavy was part of the solution...it was the part to brick the ASICs. Yet, even with ASIC out of the picture it was still possible to network hop if you had a large GPU farm and could do as you mention, join and sweep up some easy diff blocks then leave once the network diff adjusted leaving the rest of the network to hash away to solve a way to hard of a block. Well the Difficulty Adjustment Algorithm (DAA) was a SUMO customization of Zawy12's original work, the customization had a flaw which allowed the SUMO chain to be attacked for many easy blocks. This is why the SUMO chain is now so many blocks ahead of RYO's. Psychocrypt and Fireice collaborated with Zawy12 in refining some security issues with LWMA which he backported, and since 'Free Radical' v0.2.0 Release we've been on that DAA. As Fireice calls it, "rocking" of the network is still possible (harder to accomplish the larger the overall network hash) but the security flaws have been resolved.
|
|
|
|
casanovam
Newbie
Offline
Activity: 75
Merit: 0
|
|
August 01, 2018, 02:08:00 PM |
|
|
|
|
|
Nostradamus411
Copper Member
Newbie
Offline
Activity: 47
Merit: 0
|
|
August 02, 2018, 02:49:00 AM Last edit: September 02, 2018, 02:04:51 AM by Nostradamus411 |
|
[Ryo Currency 'Pie Orbital' 0.3.0.0]The fork will occur on block 161,500. It will add the dev fund [1].Additionally:- Fee increase to add a per-ring member component. This will provide better protection from blockchain spam that we experienced.
- More secure transaction semantics. This will provide network level protection from exploits like Monero double-tx-pubkey exploit.
- Remove variable-fee RPC calls. Fee is fixed and can be calculated without ryod.
- A lot of bugfixes.
Automatically updated blockchain download is available at: https://download.ryo-currency.com/blockchain.rawChangelog- fix wallet #44
- Implement stricter tx semantics #46
- fix get_approximate_blockchain_height #47
- improve simplewallet rescan_bc #50
- wallet rescan bug #54 #56
- add dev funds #56 #62 #64
- fix ryo units #58
- remove time lock transactions #61
- increase fee #63
- fix linux docker container #67
sha256 checksums 7ffc3754cc9bb3d2077c4d7a2311a5d8b75ba5855a63610bf194513ccc2e37c2 ryo-linux-x64-0.3.0.0.tar.xz e6366b029220561f5e00c4059f7178ff20e7947db340eba8d9d34aa4e6d98d68 ryo-macosx-x64-0.3.0.0.tar.xz 432c4c73f4be44dde21ee1d225a40bf350209d8483bc842d39314d75d9e3c839 ryo-win-x64-0.3.0.0.zip
|
|
|
|
HobbyMiner1122
Newbie
Offline
Activity: 25
Merit: 0
|
|
August 03, 2018, 03:06:57 PM |
|
Miners Join Us 0.1% Fees RYO Mining Pool Available Fast Reliable Servers We Have A Code Of Conduct For The Pool
|
|
|
|
cryptoroland
|
|
August 03, 2018, 03:16:25 PM |
|
It's good that the project is developing, but every fork is a signal about shortcomings. Ideally, forks should not be, or they should be very, very rare. I hope in the near future there will not be another fork)
|
|
|
|
kesior
Newbie
Offline
Activity: 63
Merit: 0
|
|
August 03, 2018, 04:50:58 PM Last edit: August 04, 2018, 06:31:42 PM by kesior |
|
Ryovolution Podcast EPISODE 1 - NOW AVAILABLE @ https://ryo-currency.com/ryovolution-podcast/
Topic: How the Ryo team was formed and clarifications of FUD
|
|
|
|
kesior
Newbie
Offline
Activity: 63
Merit: 0
|
|
August 04, 2018, 06:21:12 PM |
|
|
|
|
|
casanovam
Newbie
Offline
Activity: 75
Merit: 0
|
|
August 05, 2018, 11:53:50 AM |
|
|
|
|
|
0verseer
|
|
August 05, 2018, 11:58:39 AM |
|
It's good that the project is developing, but every fork is a signal about shortcomings. Ideally, forks should not be, or they should be very, very rare. I hope in the near future there will not be another fork) Agree, it's a bit confusing for new users.
|
|
|
|
ttookk
|
|
August 06, 2018, 08:12:03 AM |
|
It's good that the project is developing, but every fork is a signal about shortcomings. Ideally, forks should not be, or they should be very, very rare. I hope in the near future there will not be another fork) Agree, it's a bit confusing for new users. Well, as far as I know, Monero has scheduled hardforks every six months. They are mostly important for the miners, I am not sure whether users really have to go along with every single one. The basic idea is that you have a given schedule to follow. Miners know what to look for and you have the ability to push just about anything if needed. I'm not sure whether Ryo said anything about adopting this mechanism, though.
|
|
|
|
visdude
Legendary
Offline
Activity: 1081
Merit: 1001
|
|
August 06, 2018, 09:07:02 AM |
|
[Ryo Currency 'Pie Orbital' 0.3.0.0]The fork will occur on block 161,500. It will add the dev fund [1].Additionally:- Fee increase to add a per-ring member component. This will provide better protection from blockchain spam that we experienced.
- More secure transaction semantics. This will provide network level protection from exploits like Monero double-tx-pubkey exploit.
- Remove variable-fee RPC calls. Fee is fixed and can be calculated without ryod.
- A lot of bugfixes.
Automatically updated blockchain download is available at: https://download.ryo-currency.com/blockchain.rawChangelog- fix wallet #44
- Implement stricter tx semantics #46
- fix get_approximate_blockchain_height #47
- improve simplewallet rescan_bc #50
- wallet rescan bug #54 #56
- add dev funds #56 #62 #64
- fix ryo units #58
- remove time lock transactions #61
- increase fee #63
- fix linux docker container #67
sha256 checksums 7ffc3754cc9bb3d2077c4d7a2311a5d8b75ba5855a63610bf194513ccc2e37c2 ryo-linux-x64-0.3.0.0.tar.xz e6366b029220561f5e00c4059f7178ff20e7947db340eba8d9d34aa4e6d98d68 ryo-macosx-x64-0.3.0.0.tar.xz 432c4c73f4be44dde21ee1d225a40bf350209d8483bc842d39314d75d9e3c839 ryo-win-x64-0.3.0.0.zip Will the GUI wallet release soon follow in time for the stated fork?
|
|
|
|
RyoCurrency (OP)
Copper Member
Jr. Member
Offline
Activity: 195
Merit: 1
|
|
August 07, 2018, 08:22:57 PM |
|
|
|
|
|
Nostradamus411
Copper Member
Newbie
Offline
Activity: 47
Merit: 0
|
|
August 07, 2018, 10:32:22 PM |
|
Will the GUI wallet release soon follow in time for the stated fork?
Yup,
|
|
|
|
Nostradamus411
Copper Member
Newbie
Offline
Activity: 47
Merit: 0
|
|
August 07, 2018, 10:34:02 PM Last edit: August 08, 2018, 04:01:52 AM by Nostradamus411 |
|
Just to gussy up Ryo's post on the GUI a tiny bit.... New Full GUI Wallet & LITE Wallet have been released. This version includes binaries from RyoCurrency 0.3.0.0 'Pie Orbital' and fixes the bug where restoring from seed sometimes shows a zero balance in the GUI. 🤓
|
|
|
|
|