[XMR] Monero - A secure, private, untraceable cryptocurrency

[dEBRUYNE]

re: RandomX

https://twitter.com/monero/status/1133402174283767809

[Iamtutut]

Indeed, thanks.

[Hueristic]

re: RandomX

https://twitter.com/monero/status/1133402174283767809

Perfect, thx.

[Millionero]

When pruning?

[dEBRUYNE]

When pruning?

Will be available in the upcoming v0.14.1.0 release.

[Millionero]

Does that mean October?

[dEBRUYNE]

Does that mean October?

0.14.1.0 should be out soon. 0.15.x will be the September/October release.

[Febo]

Does that mean October?

Hard to believe any other month then June.

[Globb0]

Good Monero coffee chat


https://www.youtube.com/watch?v=TEWloLhVHWQ

[versprichnix]

I have rising difficulties to hold my core wallet in sync. wallet version 0.14.0.2 on ubuntu 18.04 LTS. I have many log messages like "There were 0 blocks in the last 90 minutes". From time to time I can reach the last block with patience. Any hint?

[anubizz]

Same here! 
I am running my own monero node on a single board computer (cubietruck+ 120 gb ssd) now for some time. But syncing through TOR and behind openvpn seemed to slow for full sync. I only reach 98-99,7% and still 8000 blocks missing after more then ten days.

Now after some days, changing to normal internet connection, and changing swappines of swap, i reach 99,7% sync. Thats a problem i cant solve because there is no error or similar, so no point to start changing something.

is there something else that can cause that problem?

and my secound question:
Are there any benifits from running my own local node behind a vpn or tor connection? Or does running over normal internet and only „within lan“ use protect enough and there is no ip faking nessesary?

[jwinterm]

Same here! 
I am running my own monero node on a single board computer (cubietruck+ 120 gb ssd) now for some time. But syncing through TOR and behind openvpn seemed to slow for full sync. I only reach 98-99,7% and still 8000 blocks missing after more then ten days.

Now after some days, changing to normal internet connection, and changing swappines of swap, i reach 99,7% sync. Thats a problem i cant solve because there is no error or similar, so no point to start changing something.

is there something else that can cause that problem?

and my secound question:
Are there any benifits from running my own local node behind a vpn or tor connection? Or does running over normal internet and only „within lan“ use protect enough and there is no ip faking nessesary?

I think unless you're super paranoid it's fine to run a node over normal internet, and you can just broadcast transactions over tor.
https://github.com/monero-project/monero/blob/master/ANONYMITY_NETWORKS.md

[7jaka7]

Release of Exa Wallet — mobile wallet with multisignatures support:
https://www.reddit.com/r/Monero/comments/bwase5/release_of_exa_wallet_mobile_wallet_with/

First multisignature wallet if I am not mistaken. Did anyone try it already?

[dEBRUYNE]

I have rising difficulties to hold my core wallet in sync. wallet version 0.14.0.2 on ubuntu 18.04 LTS. I have many log messages like "There were 0 blocks in the last 90 minutes". From time to time I can reach the last block with patience. Any hint?

JIT not being enabled in v0.14.0.2 significantly decreases performance. In addition, v0.14.0.2 is based on inefficient sync code present in v0.13. Both these issues will be resolved in v0.14.1 though, which is expected to be released soon (I cannot provide a specific ETA unfortunately).

[anubizz]

Same here! 
I am running my own monero node on a single board computer (cubietruck+ 120 gb ssd) now for some time. But syncing through TOR and behind openvpn seemed to slow for full sync. I only reach 98-99,7% and still 8000 blocks missing after more then ten days.

Now after some days, changing to normal internet connection, and changing swappines of swap, i reach 99,7% sync. Thats a problem i cant solve because there is no error or similar, so no point to start changing something.

is there something else that can cause that problem?

and my secound question:
Are there any benifits from running my own local node behind a vpn or tor connection? Or does running over normal internet and only „within lan“ use protect enough and there is no ip faking nessesary?

This applies to your case too:

JIT not being enabled in v0.14.0.2 significantly decreases performance. In addition, v0.14.0.2 is based on inefficient sync code present in v0.13. Both these issues will be resolved in v0.14.1 though, which is expected to be released soon (I cannot provide a specific ETA unfortunately).

Additionally, could you perhaps type status into monerod and post the output here?

Seems not to be needet any more. I checked the monerod status yesterday and with normal internet connection i reached 100% sync now.
In case that my home IP address does not get connected to my transactions in the blockchain, when i use the node with normal internet, its not a problem for me to run the node this way.
The wallet and GUI would be behind TOR or Openvpn of corse.

[JasonXIII]

Release of Exa Wallet — mobile wallet with multisignatures support:
https://www.reddit.com/r/Monero/comments/bwase5/release_of_exa_wallet_mobile_wallet_with/

First multisignature wallet if I am not mistaken. Did anyone try it already?

Hello I see it's for iOs and Android.
But it's only a mobile wallet? There is no desktop version?

[7jaka7]

Release of Exa Wallet — mobile wallet with multisignatures support:
https://www.reddit.com/r/Monero/comments/bwase5/release_of_exa_wallet_mobile_wallet_with/

First multisignature wallet if I am not mistaken. Did anyone try it already?

Hello I see it's for iOs and Android.
But it's only a mobile wallet? There is no desktop version?

Copied from the source:

— Mobile only? Any plans for a desktop app?

At this point, we're working on a fork of monero-wallet-gui to support the same workflow of multisignature wallets.

[versprichnix]

...

JIT not being enabled in v0.14.0.2 significantly decreases performance. In addition, v0.14.0.2 is based on inefficient sync code present in v0.13. Both these issues will be resolved in v0.14.1 though, which is expected to be released soon (I cannot provide a specific ETA unfortunately).

Additionally, could you perhaps type status into monerod and post the output here?

At this time my node is in sync. The answer of command "status" is:

Height: 1849876/1849876 (100.0%) on mainnet, not mining, net hash 326.75 MH/s, v11, up to date, 4(out)+0(in) connections, uptime 0d 0h 0m 17s

This is a frequent log output of monerod:

2019-06-04 23:04:57.839   [P2P6]   WARN    net.dns   src/common/dns_utils.cpp:519   WARNING: no two valid MoneroPulse DNS checkpoint records were received
2019-06-04 23:18:58.615   [P2P4]   WARN    global   src/p2p/net_node.inl:1338   No incoming connections - check firewalls/routers allow port 18080

[Hueristic]

[Monero-announce] Long Payment ID Deprecation

Dear participants of the Monero ecosystem,

We would like to inform you that we will be phasing out long payment
IDs this year. Long payment IDs are detrimental to privacy and a
source of negative user experience (as well as additional support work
for services). Services will have to upgrade to either integrated
addresses or subaddresses. Note, however, that there is some
discussion about phasing out integrated addresses as well. Therefore,
services are, to avoid having to potentially perform additional work,
encouraged to upgrade to subaddresses directly.

Long payment IDs will be phased out because they have several salient
drawbacks. First, long payment IDs are detrimental to privacy insofar
as they can potentially link the transactions of a user in case of
reusage. Second, long payment IDs have to be attached separately to a
transaction. This is inconsistent with conventional cryptocurrency
transactions and therefore unintuitive for the user. As a result,
users occasionally forget to attach the long payment ID when sending
their transaction to a service and thus have to go through support to
'recover' their funds. Third, it logically follows from the previous
point that long payment IDs cause additional support work for
services. Fourth, only one long payment ID can be attached to a
transaction. Thus, services cannot batch withdrawals of multiple users
specifying a long payment ID. By contrast, subaddresses have no such
restriction and withdrawals can thus all be batched.

In sum, payment IDs have serveral salient drawbacks and will therefore
be phased out. Services are recommended to upgrade to subaddresses as
soon as possible. Subaddresses essentially function similar to Bitcoin
HD wallets and should thus be relatively straightforward to implement.
Furthermore, subaddresses are managable from a resource point point of
view.

Yours sincerely,

The Monero dev community

https://github.com/monero-project/monero/issues/3772

[dEBRUYNE]

...

JIT not being enabled in v0.14.0.2 significantly decreases performance. In addition, v0.14.0.2 is based on inefficient sync code present in v0.13. Both these issues will be resolved in v0.14.1 though, which is expected to be released soon (I cannot provide a specific ETA unfortunately).

Additionally, could you perhaps type status into monerod and post the output here?

At this time my node is in sync. The answer of command "status" is:

Height: 1849876/1849876 (100.0%) on mainnet, not mining, net hash 326.75 MH/s, v11, up to date, 4(out)+0(in) connections, uptime 0d 0h 0m 17s

This is a frequent log output of monerod:

2019-06-04 23:04:57.839   [P2P6]   WARN    net.dns   src/common/dns_utils.cpp:519   WARNING: no two valid MoneroPulse DNS checkpoint records were received
2019-06-04 23:18:58.615   [P2P4]   WARN    global   src/p2p/net_node.inl:1338   No incoming connections - check firewalls/routers allow port 18080

That looks fine. Regarding the warnings:

1. https://monero.stackexchange.com/search?q=moneropulse

2. No incoming connections does not inhibit your daemon (monerod) from syncing properly. However, to 'seed' (i.e. serve) the blockchain to others, you'd need incoming connections, which you can get by forwarding port 18080.