bitebits
Legendary
Offline
Activity: 2236
Merit: 3459
Flippin' burgers since 1163.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 07:58:36 AM |
|
Nethash has dropped but difficulty remains the same, how is that so? Difficulty is the product of Nethash. I thought they go together.... Makes no sense ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fprntscr.com%2Fmvsezv&t=665&c=HUcsue5FMpaBtA) ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fprntscr.com%2Fmvsevm&t=665&c=1gXTiaXaoyMTnA) https://www.reddit.com/r/Monero/comments/az5on0/comment/ei5znt7smooth_xmrXMR Core Team • 10h Hash rate can only be estimated not measured directly. Until there are enough blocks upon which to base the estimate, the estimate won't be accurate.
|
- You can figure out what will happen, not when /Warren Buffett - Pay any Bitcoin address privately with a little help of Monero.
|
|
|
JW_B
Newbie
Offline
Activity: 31
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 08:47:30 AM |
|
Network Hashrate 942.12 MH/s 84.3 % unknown
something wrong...
|
|
|
|
Iamtutut
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 09:37:19 AM |
|
Is the HR per GPU the same ?
|
|
|
|
florida.haunted
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 10:03:38 AM |
|
Network Hashrate 942.12 MH/s 84.3 % unknown
something wrong...
The Difficulty will adjust automatically within 24-48h. Look: https://miningpoolstats.stream/moneroNote, known pools have only ~168 MH/s now instead of typical ~325. Network hashrate is calculated based on Difficulty and thus has some inertia. Previous time hard fork happened, I remember Difficulty was adjusting within more than 24h, closer to 48h.
|
|
|
|
Sellman
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 10:12:58 AM |
|
The Difficulty will adjust automatically within 24-48h.
It is one of the greatest and most advantageous specifications of Monero. Faster required time to adjust difficulty of network, it is truly faster than bitcoin network. The specification of Monero also help its to be more flexible and adaptable to serious changes on network, and somehow can better prevent network clogs due to extremely high difficulty, miner abandonment, and lack of resources on the main net to confirm transactions.
|
|
|
|
JW_B
Newbie
Offline
Activity: 31
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 12:58:06 PM |
|
Network Hashrate 942.12 MH/s 84.3 % unknown
something wrong...
The Difficulty will adjust automatically within 24-48h. Look: https://miningpoolstats.stream/moneroNote, known pools have only ~168 MH/s now instead of typical ~325. Network hashrate is calculated based on Difficulty and thus has some inertia. Previous time hard fork happened, I remember Difficulty was adjusting within more than 24h, closer to 48h. thats nice~ thank you
|
|
|
|
|
hashcity team
Newbie
Offline
Activity: 3
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 06:43:55 PM |
|
www.hashcity.org - PPS mining pool for [XMR] Monero-Unique functional interface -Payments at least 2 times a day -0% withdrawal fee -Functional telegram bot https://t.me/HashCityBot -pool fee - 0% until March 20 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Welcome ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
|
Febo
Legendary
Offline
Activity: 2730
Merit: 1288
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2019, 08:57:42 PM |
|
Proof-of-Work always seriously damage our planet's environment, no matter what the algorithm is for CPUs, GPUs, or ASICs.
It do not when only renewable energy is used. There is enough renewable energy fro just everything. All we need is to seize it.
|
|
|
|
Kryptowerk
Legendary
Offline
Activity: 2086
Merit: 1403
Disobey.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 11, 2019, 10:58:57 AM |
|
Hi guys. A friend of mine recently got this message when running the latest full node: WARN cn src/cryptonote_core/cryptonote_core.cpp:1767 There were 5 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack. Or it could be just sheer bad luck I assume this was just a temporary issue due to the fork and some drastic changes in hash-rate. Or is there some other issue? Thanks for your help.
|
|
|
|
Febo
Legendary
Offline
Activity: 2730
Merit: 1288
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 11, 2019, 12:24:35 PM Last edit: March 11, 2019, 02:46:53 PM by Febo Merited by Kryptowerk (1) |
|
Hi guys. A friend of mine recently got this message when running the latest full node: WARN cn src/cryptonote_core/cryptonote_core.cpp:1767 There were 5 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack. Or it could be just sheer bad luck I assume this was just a temporary issue due to the fork and some drastic changes in hash-rate. Or is there some other issue? Thanks for your help. Yes since ASIC miners cant mine anymore overall hashrate decreased by factor 3 or 4. soon we should get final number. But also now new GPU miners will start flocking back in, and hash rate will start growing back, since Monero is probably super worth to mine now for them. You can see here https://www.coinwarz.com/difficulty-charts/monero-difficulty-chart Difficulty is at 1/3 now.
|
|
|
|
dEBRUYNE
Legendary
Offline
Activity: 2268
Merit: 1141
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 11, 2019, 07:17:42 PM |
|
Hi guys. A friend of mine recently got this message when running the latest full node: WARN cn src/cryptonote_core/cryptonote_core.cpp:1767 There were 5 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack. Or it could be just sheer bad luck I assume this was just a temporary issue due to the fork and some drastic changes in hash-rate. Or is there some other issue? Thanks for your help. See: https://www.reddit.com/r/monerosupport/comments/azif9x/repeated_message_issue/
|
|
|
|
Whtwabbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 11, 2019, 08:50:19 PM |
|
Does the new mining algorithm give less of a hashrate?
I notice that the hashrate is now sitting at 250MH/s, I have been mining with xmrig with a RX 470 and are getting around 100h/s I'm sure before the first asic algo update I was getting over 200h/s on the same card does this mean the algo now @250MH/s makes the network secure as it would have been with 500MH/s back then?
Or is my configuration most probably shite?
|
██████████ ██████████████████ ██████████████████████ ██████████████████████████ ████████████████████████████ ██████████████████████████████ ████████████████████████████████ ████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ████████████████████████████████ ██████████████ ██████████████ ████████████████████████████ ██████████████████████████ ██████████████████████ ██████████████████ ██████████ Monero
|
| "The difference between bad and well-developed digital cash will determine whether we have a dictatorship or a real democracy." David Chaum 1996 "Fungibility provides privacy as a side effect." Adam Back 2014
|
| | |
|
|
|
TheFuzzStone
Legendary
Offline
Activity: 1512
Merit: 1442
thefuzzstone.github.io
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 11, 2019, 09:49:06 PM |
|
|
|
|
|
equipoise
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 11, 2019, 10:47:42 PM |
|
Does the new mining algorithm give less of a hashrate?
I notice that the hashrate is now sitting at 250MH/s, I have been mining with xmrig with a RX 470 and are getting around 100h/s I'm sure before the first asic algo update I was getting over 200h/s on the same card does this mean the algo now @250MH/s makes the network secure as it would have been with 500MH/s back then?
Or is my configuration most probably shite?
RX 470 getting 930+ h/s with Samsung memory and 800+ with other memory. Check your miner/config/bios.
|
|
|
|
|
florida.haunted
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 12, 2019, 07:41:35 PM |
|
In that discussion, as I've understood, sech1 focuses on the problem to make ASICs as efficient and as complicated as Intel CPU. linzhi-sonia says it will try because he likes this stuff with ASICs and their developing. What I think? We should focus on TRUE randomness instead of making mining algo to be too difficult for ASICs just because complicated design of the algo, for example, adding a true virtual machine level into algo design, like somewhat done in RandomX. Currently, cn/r uses block height as a source of randomness. And as linzhi-sonia mentioned, he will just add an interpreter or pre-compiled parts to the algo, because block height is known in advance to the future. I propose to add TRUE random generator via external ORACLES (like oracles work in Ethereum contracts). Or, good source of true randomness is LONG hash of all the transactions in last 100 blocks for example. Thus linzhi-sonia can't predict and pre-compile no parts of mining algo. Also we may dream about FLOATING POINT mining algo based on fining solutions of differential or integral equations of random nature. Finally we may focus on solution findings of SYMBOLIC mathematical problems, randomly generated. What do you think, Community?
|
|
|
|
jwinterm
Legendary
Offline
Activity: 3108
Merit: 1115
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 12, 2019, 07:55:33 PM |
|
In that discussion, as I've understood, sech1 focuses on the problem to make ASICs as efficient and as complicated as Intel CPU. linzhi-sonia says it will try because he likes this stuff with ASICs and their developing. What I think? We should focus on TRUE randomness instead of making mining algo to be too difficult for ASICs just because complicated design of the algo, for example, adding a true virtual machine level into algo design, like somewhat done in RandomX. Currently, cn/r uses block height as a source of randomness. And as linzhi-sonia mentioned, he will just add an interpreter or pre-compiled parts to the algo, because block height is known in advance to the future. I propose to add TRUE random generator via external ORACLES (like oracles work in Ethereum contracts). Or, good source of true randomness is LONG hash of all the transactions in last 100 blocks for example. Thus linzhi-sonia can't predict and pre-compile no parts of mining algo. Also we may dream about FLOATING POINT mining algo based on fining solutions of differential or integral equations of random nature. Finally we may focus on solution findings of SYMBOLIC mathematical problems, randomly generated. What do you think, Community? There's an active issue thread on GitHub discussing options for PoW moving forward: https://github.com/monero-project/meta/issues/316
|
|
|
|
lncm
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 388
Merit: 13
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 13, 2019, 11:52:49 AM Last edit: March 13, 2019, 12:19:40 PM by lncm |
|
I can't open my monero Legder wallet with 0.14. I got "Could't open wallet. Wrong Device status : SW=6e00 (EXPECT=9000, MASK=ffff)".
Any ideas?
EDIT - forget it, I was on firmware 1.4.2. Updated Ledger live and firmware to 1.5.5 and now it works.
|
|
|
|
dEBRUYNE
Legendary
Offline
Activity: 2268
Merit: 1141
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 13, 2019, 01:22:37 PM |
|
I can't open my monero Legder wallet with 0.14. I got "Could't open wallet. Wrong Device status : SW=6e00 (EXPECT=9000, MASK=ffff)".
Any ideas?
EDIT - forget it, I was on firmware 1.4.2. Updated Ledger live and firmware to 1.5.5 and now it works.
Please not that there is a bug in Ledger Monero app v1.1.3. Therefore, Ledger Monero users are advised not to use their wallets until Ledger Monero app v1.2.x is out. https://www.reddit.com/r/Monero/comments/b0jjgc/missing_xmr/eif5jdl/
|
|
|
|
|