Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 133. (Read 4671920 times)

Code should be tested properly before releasing! So I think I can assume it'll work ... Also the fork already happened couple of hundreds blocks ago ..

Wait if you sent with the latest code update. It is never a good idea to make an important transaction during a scheduled update (Soft Fork, network upgrade...Idunno what to call it anymore).

Thanks for help ! Now all ok !!

is monero havion trouble with the new update?
anything about chain splits known?
I have a transaction which is stuck in the network and only few monero block explorers show the transaction. Others don't

Transaction is a6b77e6be1ecfa5b852463290b20fafa55821bd12817df735b3ec1108ca6d256

https://moneroblocks.info/search/a6b77e6be1ecfa5b852463290b20fafa55821bd12817df735b3ec1108ca6d256 (not available)

working:
https://xmrchain.net/search?value=a6b77e6be1ecfa5b852463290b20fafa55821bd12817df735b3ec1108ca6d256
https://monerohash.com/explorer/search?value=a6b77e6be1ecfa5b852463290b20fafa55821bd12817df735b3ec1108ca6d256

I send to cryptopia and cryptopia says 4/20 confirmations.
How can it be that the transaction is gone from the network?

What can I do?

Edit: of course using the newest monero version (wallet cli and monerod) My local blockchain was upgraded without problems ..

Port forwarding is not required and everything will work normally, but if you want to help the network more then you should forward the port 18080. That way other peers can connect to you.

EDIT: Oops quote fail corrected.

After i upgrade to most recent version, i keep receive message "WARN    global  src/p2p/net_node.inl:1338       No incoming connections - check firewalls/routers allow port 18080". Should i leave it alone or configure my firewall or/and router?


It took some time since it actually upgrade database version, not sync process. In my case, restart both CLI and monerod fix the problem.

I closely follow the team of developers and the coin itself, monero remain true to themselves and their configuration
Zcash requires further development and real anonymity.

You can resolve your issue by following this guide:

https://monero.stackexchange.com/questions/10364/gui-v0-13-0-3-does-not-start-on-mac-os-x-monero-wallet-gui-cannot-be-opened-bec

Alternatively, use the buildbot binaries that selsta posted here:

https://www.reddit.com/r/Monero/comments/9pdxfg/gui_v01304_mac_osx_bug_fix_timeline/e810n1d/

Hello guys
Version: 0.13.0.3 for Mac OS  64  works ?
When push after download have error :

Contact the developer to make sure that monero-wallet-gui works with this version of macOS. You may need to reinstall the program. Make sure that all available program updates and macOS are installed.

Now GUI v0.12.3.0  and Mac OS High Siera 10.13.6 .

Same error  and on Mojave

Could you post (or PM me) the status output of monerod?

Trusted setup for Zcash is a concern for some but objectively PIRATE is the best version of zcash tech (no founders tax, default anon z tx, fair launch), so if you're going to own any zk snark based coin as a backup for XMR PIRATE is the only realistic choice.






I agree XMR tail emission is a great feature and prevents problems in later years, and the 'infinite' supply in the comparison chart is a bit cheeky (I didn't make it). Monero is still the premier privacy coin and has the first mover advantage and a big network effect, BUT, PIRATE is the next best choice for fungible digital cash, and there are always bugs and non zero chance XMR has future catastrophic event, so having PIRATE as a backup digital cash for XMR in the cryptosphere is a good thing!

Digital Cash isn't like the Highlander, there can be more than one!

WTF is going on with da fork?
Our exchange using only CLI.
Now all we see SYNCHRONIZATION STARTED.
Everything is updated. But synchronization going forever.

Should we restart  our exchange https://exbase.net

or just wait?

Can someone tell me why with new XMR-Stak 2.5.1 I get the error:

Thread 0 has invalid config. ?

I post this config, works perfectly until 18th October fork and new xmr-stak 2.5.1.

"gpu_threads_conf" : [
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 0,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 1,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 1,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 1,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 2,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 2,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 3,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 3,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 4,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 4,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 5,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 5,
    "intensity" : 1760, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

],

It could be that the remote node you are (were) using was still running an old version.

The issue will be fixed in the upcoming GUI v0.13.0.4.

Pinging @Globb0 too.

hello,

is the wolf cpu miner updated for this fork?
i am facing difficulties installing on a linux system (am very newbie), am also trying to connect remotely with limited access.

can someone please upalod a fully working cpuminer for linux as I can copy it the folder and run it.

appreciate it. thanks.

@extenami  That pie is much different only 1h latter as yours were made.  It will take few days to stabilize.  I dont expect any serious change in hash rate or pool distribution. And not much Monero is mined in China at all.


Such things happens when you upgrade protocol in cryptocurrencies. We should remember why this protocol upgrades are done. I found this on reddit. A half cent transaction fee.

OK, it's a known issue. But I tried all the workarounds suggested and I still can't access my wallet...

https://i.imgur.com/ZoL7Z1B.png

Hello, fellow miners!


Features:
- email notifications of workers down
- stats and hashrate chart per worker
- PPLNS reward scheme for rounds shorter than hour, PROP scheme for longer rounds, PPLNS window is 60 minutes
- PPS reward scheme on ports: 3331, 5551, 7771
- payment id, integrated address, subaddress supported
- adjustable payment threshold
- every port supports secure SSL/TLS connection as well as insecure one
- static diff supported, see static diff calculator
- multiple daemons, to prevent downtime in case of daemon stuck
- height checks, to prevent mining on forked chain
- sample configs for cn-v8 supported mining apps

PPLNS fee: 0.9%
PPS fee: 0.9%

Location: Europe

Welcome & Lucky Mining!