Show Posts
|
Pages: [1] 2 3 »
|
So I've run the daemon the other day to sync it after a long time (months) and it kept getting visited by the OOM killer. I had 2 GB ram on that machine and after increasing to 4GB that stopped. What is the current minimum amount of ram necessary for monerod these days?
|
|
|
... there are only around 1000 Monero nodes
Why do you think 1000 is a low number for Monero? I'm not saying it's high, or even enough, but I don't see any indication that would make me believe that it's the opposite. Have you seen any reports from people trying to set up their own node and not being able to sync because of lack of open nodes with available outgoing connections?
|
|
|
Hi, monero-gui-v0.17.2.2 not visible balance and history transaction if old key import. Impossible restore wallet from seed, next button inactive. Wallet often freezing. OS: Debian9.
Debian9 is quite old (11 was just released), not sure the devs are still targeting that. Try and restore on a more recent linux version.
|
|
|
Haven't seen this information posted here, so here it is: 0.17.2.0 (both CLI and GUI) was released.
Congratulations to the developers for bringing out further improvements to this project!
And many thanks for all the hard work you have put in, mostly for free. I don't think you guys receive enough praise.
|
|
|
I figured the .keys was probably the best route, but it keeps telling me incorrect password. What a mess-up on my part...I copied the seed word for word, the restore height, and password the second I created the file. Who knows, maybe I missed a letter/number/character when copying the password. What a learning lesson. I am going to guess it is just lost at this point if there is no way for Binance reverse the transaction. That was a semi-expensive learning lesson. Could have been much worse.
Thank you for the help!
Did you by any chance get the idea while writing down the seed to swap a couple of words around, and forgot about it?
|
|
|
Also, scroll down a little for this:
|
|
|
the same with bitmonero.log log level 3
You probably have another instance running. I see this in your log: 2020-12-26 16:25:02.558 7f2b41bcb780 ERROR net contrib/epee/include/net/abstract_tcp_server2.inl:1023 Failed to bind IPv4: bind: Address already in use 2020-12-26 16:25:02.558 7f2b41bcb780 FATAL net contrib/epee/include/net/abstract_tcp_server2.inl:1072 Error starting server: Failed to bind IPv4 (set to required) Restart the computer and try again.
|
|
|
@asteinbe Do you need to run it as a service? First check if the daemon launches alright and syncs with the network, by just running monerod in a separate console or screen. Make sure you do this on an SSD and you have at least 100GB free.
|
|
|
Monerans feels about right.
I'm not sure about that. If you take out the second syllable you end up with: mo-rans
|
|
|
I have updated my daemon to 0.17.1.1 and it threw some errors when it started: 2020-10-19 11:19:11.301 7ff01dcfc780 INFO logging contrib/epee/src/mlog.cpp:273 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,daemon.rpc:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO 2020-10-19 11:19:11.302 7ff01dcfc780 INFO global src/daemon/main.cpp:293 Monero 'Oxygen Orion' (v0.17.1.1-release) 2020-10-19 11:19:11.302 7ff01dcfc780 INFO msgwriter src/common/scoped_message_writer.h:102 Forking to background... 2020-10-19 11:19:11.304 7ff01dcfc780 WARNING daemon src/daemon/executor.cpp:61 Monero 'Oxygen Orion' (v0.17.1.1-release) Daemonised 2020-10-19 11:19:11.304 7ff01dcfc780 INFO global src/daemon/protocol.h:53 Initializing cryptonote protocol... 2020-10-19 11:19:11.304 7ff01dcfc780 INFO global src/daemon/protocol.h:58 Cryptonote protocol initialized OK 2020-10-19 11:19:11.305 7ff01dcfc780 INFO global src/daemon/core.h:63 Initializing core... 2020-10-19 11:19:11.305 7ff01dcfc780 INFO global src/cryptonote_core/cryptonote_core.cpp:515 Loading blockchain from folder /blabla/.bitmonero/lmdb ... 2020-10-19 11:19:11.876 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<cbc84653d98a3d94f87a53781170dfb2e651a734d01a593e456d3590a5476983> 2020-10-19 11:19:11.876 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <1e35055758ad7e5953402ced23826708b7195f3d7ea6613dc2987851d3deb009> 2020-10-19 11:19:11.876 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<96f2994157218152d69c2e3a57f1ff835a851ddcb80aa60e42f008ec1d6b2990> 2020-10-19 11:19:11.876 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <a18690fb22a57b02209bef9ef0ddbf2de1323133f368bcbfc7e375efc2d9920e> 2020-10-19 11:19:11.877 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<8fafeb4321a5f332f91153ba0b275b2558fb037b3ac5a84dcd828946c3c819c2> 2020-10-19 11:19:11.877 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <2668d73c7b651851c8372d1079c2589ffc7b5130ed2574d6ada62a71c37d810f> 2020-10-19 11:19:11.877 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<92f9f5ee7536418fd945696c2ede870330beb780aeb38ad83669ac8e9cdd1a24> 2020-10-19 11:19:11.877 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <0df766ab3943fd9c4d7b520d29cba67adbb635243dbcdb9837aed84f282f5f15> 2020-10-19 11:19:11.877 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<e95b4e3e06186442c06c8c5c00b5b2b471fc5f18e39ac4ae498dab08feeb03d5> 2020-10-19 11:19:11.877 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <83bfb664c750a7a736cf59df88e14c407e345db1358ba359a29a6f7f1c7b2e16> 2020-10-19 11:19:11.878 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<f21ed774365ab27525de21b169de0ffd724efe71cd2444d69d5597635e7fc47f> 2020-10-19 11:19:11.878 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <b655db9d253c601462a8bf65f04ea49c6fa3308696136f91670d167cb8a81530> 2020-10-19 11:19:11.878 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<e770f17f5d8393d47e6d0adb53803a9ba19be6c0b253eab3fcf2e7cc79939fa2> 2020-10-19 11:19:11.878 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <adcf277aaed827bb3653de619243d90812b617a1385cf9e45e1bbd0dad28264e> 2020-10-19 11:19:11.878 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<fdc4bacad7da0a9eaa9c60e6c2e5d11fd1924b8a404b1bb755dcd135df093e77> 2020-10-19 11:19:11.878 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <3a8c563771277c7804505d202c860cf4bcceb2134bd2b1eba48c61cdfd69bb59> 2020-10-19 11:19:11.879 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<994fb4f582020a5a227067b2ba8d07a756e0e593e92f4655f5bb59e118a63915> 2020-10-19 11:19:11.879 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <aa59568de116ef706603eff6d12084c7340aca236dad4d8b6e2bb026ffe52563> 2020-10-19 11:19:11.879 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<f5961335c0b43732e43e46847a455fd24ebc9b9ff99e152c7204f0346c17a4a7> 2020-10-19 11:19:11.879 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <153850f6115baeec2f0529dfc351d96de78b7349ea2836a9c6821a3b93fe4a65> 2020-10-19 11:19:11.880 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<84eda9824561192922999d8a529a95ad46f4dbfd03613d0bc1ab73a72370d662> 2020-10-19 11:19:11.880 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <5ec19f53f392f0b28d99f28f07bfa36758cac0a1a291d4f6e85062a49d135065> 2020-10-19 11:19:11.880 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<887e5dc4cf350b637cbcc7040ee6cc18aae7b5222375a4bc16e842dc0d58e7d8> 2020-10-19 11:19:11.880 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <f9ce819d6a5e2055dc8d1e5bc83f6a706e42fc60087423ccf986565866f6d06f> 2020-10-19 11:19:11.881 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<e7cd4fc28ff0149f19299ba2baacead95a31dca809530ec8bff18ed2f36719b0> 2020-10-19 11:19:11.881 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <624419c9098a3f8eb30f256af70fb6d9b50cbee26d7166ca21f42e11be09977d> 2020-10-19 11:19:11.881 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<b95fed227c3fe6a92f2085bb438606ac10eb9b591ecec0ebd215518ead6c7f4d> 2020-10-19 11:19:11.882 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <9a69b1d95241c75949141c9360f38f6f0e46cc36db314c9caba6b87014309b80> 2020-10-19 11:19:11.882 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<29d91127f3786987abcc687cacde2188c32accf3ebb0ff5ba03342bb46169f91> 2020-10-19 11:19:11.882 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <410131349b720031c9cfcb5c540f23fc20b3201208752fbc5272a18ec47bba89> 2020-10-19 11:19:11.882 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<3db634a770ed7f712f4199432c4550a149677be97f5237d119440a6305b46e46> 2020-10-19 11:19:11.883 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <54e005b8d92a2ef6ef2c593151739d1135ad44378cf2b9ea4919bb81492bcb8c> 2020-10-19 11:19:11.883 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<74d080453c561412d34423f8121d0306fd0495d03ea5b9eb9e4caa705d595c20> 2020-10-19 11:19:11.883 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <3a4078722a683eea6c2cb636125f3bca95d4001200f96dd47b106a6c4154f38f> 2020-10-19 11:19:11.884 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<66c920e9e0e1e8fef99527d376a7b0e8cd03ff946e5afa3bae853aab614ac82d> 2020-10-19 11:19:11.884 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <76b56b96b728d3f293e241f788db73acbf5e918978ba4679d5ede369976c7596> 2020-10-19 11:19:11.884 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<caff3a3a38984b4640aeda31ef9123547962b25f5db1a1536020f43271db0b0e> 2020-10-19 11:19:11.884 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <893f6e0d795a27c6db58b5a69d2fb31fea8d28157cf46cba5c24414d05dac696> 2020-10-19 11:19:11.885 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<c1bb0007c10fe4ff41f1e61dbea45cb61a34d3a0feb2c3eb5ab1cc1d577f3fa6> 2020-10-19 11:19:11.885 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <ddcc0807364303df384b1a6e7f44ea2bd0ec1fc880856cf1d074214935ca059b> 2020-10-19 11:19:11.885 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<c8cdf73e45447880695e5faa68891be63a709524b52968f8a8f9f3d14508a78c> 2020-10-19 11:19:11.885 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <f84b47b331b5d0b4079a25e33aeeda423c108d82d5915cd61d9b31e9b86f569d> 2020-10-19 11:19:11.886 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<d753697fc86cbb7e378fc470f78b2d8886a681747d1bf2d4b537c7d576a3127f> 2020-10-19 11:19:11.886 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <8a1d661a52244e1def32a46fd07704a926c4e9a3e7c97a89748e65267bb1efb5> 2020-10-19 11:19:11.886 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<927c7c911d0b232a6bf2231a09f48d7a0c7e30b41f5288646757bb5139a94144> 2020-10-19 11:19:11.886 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <4b0bc4fd4ad04a2d7c9c77d8de077aafad4445d084730ed93f8fee89529dd0b8> 2020-10-19 11:19:11.887 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<2fc5d16a748506b321fcca91a09b665fe6f34b537ec2da921282e4d5a5614d91> 2020-10-19 11:19:11.887 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <683de639f48936b47c0085c08e6dad1861e837442514c4512f236b4d8ee247c6> 2020-10-19 11:19:11.887 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<9bba07682c36178b36ce651335491f0f9a7c923ec405e06c115e91d9a1b785be> 2020-10-19 11:19:11.887 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <50cc4fc01aa71aa421436979cef3767c0750c8ffc41c1d6442a80f4d95ec8cd5> 2020-10-19 11:19:11.887 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<b3a12ac923bb713ea3ba7f3f93773dd90a5ea4c62b5a96f311deaedcac1620c6> 2020-10-19 11:19:11.887 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <1481d858bd26bf2d4063bffbedb9ad40830110a7dd9b742e0f97f271c79ac2d8> 2020-10-19 11:19:11.888 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<b04685adbfed890dc57a3bb36f2f43110824f6f66de15b3ce29644282e853df8> 2020-10-19 11:19:11.888 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <d57f110defa6b23b5dfdf136781be5432bdfeff0a5ce4d619cf2eed4ccf790da> 2020-10-19 11:19:11.888 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<f25d71074d218c8173050b70f27c446ae015eb2e67478ec792fe879b388f11c7> 2020-10-19 11:19:11.888 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <583f1eb6f63ed8d43834ad71e10cc9b74465946960f3f8b2f2d8c674b2d0c2e0> 2020-10-19 11:19:11.888 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<f8e483f17c7c69deebb77e7b675582756b3c973873a3343870e685bf6d2123cd> 2020-10-19 11:19:11.888 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <ac509c110f856dfa28cef84c9a4a4dfbbf84a2217b1d882eebb7eb3cf45268e4> 2020-10-19 11:19:11.889 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 failed to find transaction input in key images. img=<f1ec8877b10ee179c01eab44a9a0f21ce747d54c2a0ed418766bc4b683740e41> 2020-10-19 11:19:11.889 7ff01dcfc780 ERROR txpool src/cryptonote_core/tx_pool.cpp:491 transaction id = <bbdf0586c07f4ccc462205a06226c3d0e5cdf0b634d54711d38f19b034cf5cfe> 2020-10-19 11:19:12.320 7ff01dcfc780 INFO global src/cryptonote_core/cryptonote_core.cpp:690 Loading checkpoints 2020-10-19 11:19:12.320 7ff01dcfc780 INFO global src/daemon/core.h:73 Core initialized OK 2020-10-19 11:19:12.320 7ff01dcfc780 INFO global src/daemon/p2p.h:63 Initializing p2p server... 2020-10-19 11:19:12.740 7ff01dcfc780 INFO global src/daemon/p2p.h:68 p2p server initialized OK 2020-10-19 11:19:12.741 7ff01dcfc780 INFO global src/daemon/rpc.h:63 Initializing core RPC server... 2020-10-19 11:19:12.741 7ff01dcfc780 INFO global contrib/epee/include/net/http_server_impl_base.h:79 Binding on 0.0.0.0 (IPv4):18081 2020-10-19 11:19:13.293 7ff01dcfc780 INFO global src/daemon/rpc.h:69 core RPC server initialized OK on port: 18081 2020-10-19 11:19:13.294 7ff01dcfc780 INFO global src/daemon/rpc.h:74 Starting core RPC server... 2020-10-19 11:19:13.294 [SRV_MAIN] INFO global src/daemon/rpc.h:79 core RPC server started ok 2020-10-19 11:19:13.294 [SRV_MAIN] INFO global src/daemon/daemon.cpp:213 Public RPC port 18081 will be advertised to other peers over P2P 2020-10-19 11:19:13.294 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 ********************************************************************** 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 The daemon will start synchronizing with the network. This may take a long time to complete. 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 You can set the level of process detailization through "set_log <level|categories>" command, 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING). 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 Use the "help" command to see the list of available commands. 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 Use "help <command>" to see a command's documentation. 2020-10-19 11:19:14.295 [P2P1] INFO global src/cryptonote_core/cryptonote_core.cpp:1724 ********************************************************************** It then proceeded to sync with the network. Do I have a corrupted blockchain file or something?
|
|
|
Remove most usage of Boost library Why is Monero moving away from Boost? If I remember correctly it's been heavily used ever since the code was rewritten in C++.
|
|
|
Got an email today from Freewallet, saying I need to verify my account. Hah! Those scammers won't go away, will they? Just warning you guys, never, ever go near anything related to Freewallet. Don't click on anything, don't download anything, don't follow any links, etc.
|
|
|
^ I had the same concern at the time phishead. There were only 200 nodes in total However I do think Dandelion does not resolve your ISP and others knowing there is a Monero node running on your IP address. It solves that a transaction cannot be linked to an IPadress anymore. Running a node is not illegal, I think. Let's hope that doesn't change. You don't have to own Monero to run the node.
|
|
|
Think about it practically, an ASIC is an investment in the coin. Research, design, running, costs. Its in their interest the coin is valuable.
Only if no other high-marketcap coins use that algorithm.
|
|
|
I don't trust a thing I see on that exchange anymore, I think its all smoke and mirrors using stolen coins to destroy Moneros value. It's completely controlled by institutional bankers with Zero accountability.
NO-one Should have coins on that exchange.
Which exchanges would you recommend?
|
|
|
Thank you very very much Chicken_76 for clearing that out. Unfortunately the payment ID was mandatory. So I am safe? With inputting anything there? I am crazy concerned because this is the 2nd exchange that has some issues sending out to an external wallet, my first exchange is still transfering the coins for some unknown reason for several days now and support just got back to me with a response they are looking at it. The transaction failed and no coins was refunded. And now this. I always thought and had an impression transfers were automated. Adding a payment ID should not break transaction creation. I think they still work on the network if the wallet is started with a parameter to allow them, but they're very much on their way out. As long as you entered your wallet's address correctly, you should be good. It's all in the hands of the exchange now.
|
|
|
Hello all!
Got a pretty noob and URGENT question with the payment id. I have sent a monero(exchange wallet) to my other monero wallet. And the exchange wallet requires a payment ID so i simply generated a random one from the mymonero.com web GUI. Now my Monero coins have yet to arrive for over an hour now.
Question is, is it ok to generate a random Monero payment ID when sending to another wallet? As I have read and understood this is a an ID simply to track the transfer of the coins. And the coins will still transfer with our without the ID or whatever string you input on the payment ID to the proper address.
Also how do you track Monero blocks? Because all I have from my exchange is the payment ID and no transaction blocks? And to be honest I am very worried about losing my coins!
Thanks for the enlightenment.
As a general rule, payment IDs are not necessary for transactions to go through, and if I'm not mistaken they will be deprecated in the next major version. Exchanges used to require them when receiving coins, so they know which user to credit with those coins. If you are sending the coins to a wallet you operate, you probably don't need a payment ID (unless you expect to receive the exact same amount from other sources too). That being said, if the exchange's interface has a 'payment ID' field and they made it mandatory, there's nothing you can do about that. If the exchange has indeed sent the coins, they could probably give you more information on the transaction, like in which block it was included. I would wait a bit and then contact their support.
|
|
|
Over the past 24h Bitcoin went up about 1% , but everything else with 'Bitcoin' in the name has been pumping hard:
Bitcoin Cash: 6% Bitcoin SV: 56% Bitcoin Gold: 22% Bitcoin Diamond: 53% Lightning Bitcoin: 12%
In the meantime, Monero only went up 3%. What do all these 'Bitcoin something's offer that Bitcoin + Monero do not? How can the market be so out of touch with reality?
|
|
|
What is the current Monero DAG size? Any link to follow that info?
DAG size? You are thinking about Ethereum. Monero does not have a DAG.
|
|
|
The competition is not standing idle. I don't really see Grin as a serious threat to Monero, but I DO see Litecoin as one, since it has a better image, does not have the same issues with ASICS, ... But it does, it's mined exclusively by ASICs.
|
|
|
|