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

Is it fair to say then that the system where the node runs on is not particularly resourceful? Because if so, that is partly the cause of your relatively poor performance. In addition, note that the current daemon has inefficient sync code and JIT is not enabled. Both have a serious impact on performance, which may also be partly the cause of your issue. I'd advise to give v0.14.1, once it is released, another shot, as it will have drastically better performance.

Debian Linux on both devices. So on my laptop that is connected to the node over Lan. The node is running on a cubietruck (cubieboard3) with 2gb RAM and 2gb Swap (Swap not really in use because of the speed loss when transfering the files to SSD).

Internet connection async. with 100 mbit down- and 10 mbit upload. So fast enough i think.

I still have some problems with my node. Monerod status check shows 100% sync and there are some in/out connections (about 8/6), so all ok.
But when i connect my gui and send a transaction it takes 20-30 min to fully broadcast it and get the block hight. So orders with a time limit time out before its finished to send the transaction.

At the moment the transaction was done the node had to sync another 471 blocks. And this takes to much time.
Would it be more constant if i set a „block sync size“ of 5 or 10 blocks?

You're missing one important point. Even such platforms like LocalBitcoin started delisting Monero.
If people will really start using XMR, then authorities will force bans and delistings from pretty all reliable exchanges.
The only thing that saves anon coins from disaster is that luckily they are not popular enough. Adoption will kill them.  

People often like to purport that Monero will inevitably get banned. However, the new FinCEN guidance is basically inconsistent with that notion. From the CoinCenter article:


https://coincenter.org/entry/fincen-s-new-cryptocurrency-guidance-matches-coin-center-recommendations

Arguably, this is long-term bullish for Monero.

When top mixer services shut down recent weeks, I guess that people whom want anonymous transactions might come back to more regularly use Monero as their main means of transactions. Because there is no doubt that Monero is the best (or one of the best) altcoins that can provide anonymous transactions. To reach anonymous transactions, it also requires some technical steps that should be do right and carefully from users, but at least we know that there are available featurers for anonymous transactions with Monero. It will increase total demands on Monero in short term; for long term we might have to wait for crypto bull run.

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

This is a frequent log output of monerod:

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

...

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

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

— 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.

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?

This applies to your case too:


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

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?

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?