Actual work done by MoneroV? Please give examples, because I can't see any  I'm taking their word and examples giving on this announcement - https://monerov.org/announcement-monerov-fork-date-postponed/"– MoneroV codebase is currently fully functional and tested (as can be seen in this image) on macOS Sierra, Windows, 64-bit and on Linux, 64-bit. We will use the additional time to add more supported machines." "– MoneroV’s source code, including the MoneroV GUI wallet, the MoneroV daemon and all other dependencies on our Github account (as seen in this image), Will be published on Github publicly for the community to audit before released in downloadable form." They would not be smart to not have the project open-sourced and backed by their claims. Why are you busy criticizing MoneroV when they have a community and showing genuine effort, and you aren't you all over the new last minute fork attempts? You still haven't said what the MoneroV team have actually done, aside from change the name from Monero to MoneroV in the GUI. Why are you busy criticizing MoneroV when they have a community and showing genuine effort
I don't see any effort. and you aren't you all over the new last minute fork attempts?
Not sure what you're trying to say here, but I am not a fan of Monero Classic/Monero Original/Monero0 either. |
|
|
|
DAMM. All these recent copycats of MoneroV are sprouting.
Let's hope the community will appreciate the actual work done by MoneroV, and know that the rest are just last-minute attempts.
Actual work done by MoneroV? Please give examples, because I can't see any |
|
|
|
Are you sure it wasn't your problem? Do you have 2FA enabled? Do you have malware on your computer? |
|
|
|
TOR is quite slow. Just use VPN
You have to place a lot of trust in a VPN provider (there is no way to verify a no-logging policy), and in the VPN provider's ISP. |
|
|
|
Diff is still dropping like a stone 62,340,761,652 currently, with a 24hr high of 139,157,834,962  My guess, It'll drop to around 25,xxx,xxx,xxx Based on the time between the last few blocks that seems about right. |
|
|
|
due to the fact that i want to invest in some already established crypto (which monero in my opinion definetley is) i would like to find out more about XMR, where can i find the roadmap for monero ?
There's https://getmonero.org/resources/roadmap/ but it needs updating. |
|
|
|
Hmmm... I think I made a big mistake in assuming that Hamilton can win at Bahrain with that grid penalty. It's becoming some kind of trend that Bahrain is Ferrari's race. 2018 Bahrain GP Qualifying Results A shame that Verstappen crashed out of quali  |
|
|
|
So after reading this entire thread and all published info on MoneroV I have come to my own conclusions. These opinions have no basis or fact to back them up but more of a gut feeling.
I think that it is possible that Bitmain is behind or involved with this fork as they want to keep using the ASIC's they developed. The timing of the announcements of fork coincide with the news of the Monero ASIC miners. Nothing in the MoneroV release info states ASIC resistant or any attempt to address that question. If I'm wrong, I'm open to being proven wrong. I am not here to FUD, just real questions on the ASIC topic need to be answered. Keeping core dev team a secret is a big negative in my book. Would you buy stock in a company if you did not know any information about who ran it from the top? I noticed only one person in the MoneroV ANN asked anything about ASIC mining and that questions is still not answered.
MoneroV = centralized ASIC mining consortium.
Like I said I have no fact to back this up just gut feelings. My gut feelings are usually right but I could be wrong. I have been involved with Monero since almost the beginning and I can attest the Monero community is strong and has lots of good people. I hope for the sake of people getting involved in MoneroV it is not an ASIC continuation or a scam. Time will tell and I hope this project really is on the up and up because I believe there are some good points for MoneroV and some issues addressed that are not addressed in Monero.
Please prove me wrong with facts if you have them regarding ASIC resistance. For now I have not seen any fact that lead me to believe this coin is ASIC resistant.
You've mixed your forks up (easy mistake, we have a few of those now  ). MoneroV is forking after the v7 hardfork, so they'll have the updated v7 PoW. There's a lot of reasons to hate MoneroV but this isn't one of them - Monero Classic and Monero0 are where you should direct your ASIC related hate. |
|
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Loan amount: 0.005
Loan end date: by 17.04.2018
Receiving address: 3ACcSBSDAoYK1MJHK6vku2YFyVk3FNYQ4c
Collateral: None
Hoping that you might be able to fill this. 0.0055 as payment like before.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJaxNIkAAoJEKkgyZcwTnV4azsQAJTx8cLPb4qaHKq87/fWfX+6
Q8EmERM49ycrwNJ7eXHj7YGvwJiPyU2T1wqXX49fNwIwdBkztSHGfUVank4PoWgA
LItT+UvV4Awk0+CQFGhkqWiTPYCEjhzG9b3tPollRJeXeA3/RQNTSGs/LpcHSli7
OrqJDQGleMDLaysVMH0tQsZRpPpn02tBi6iZQnLdBQp7V9/5YhSlOzoqWSUI8Z/5
XIzkoLiPFgdb3+/1nIWy2E3QEYzdJCTmGm1WAeo5vscXMs5pMdJj5VmGtq3o3oln
rUpwSIHaQQokjZ55DjSwkUDCyskgfdniMi4U9f4Sl//YYu2/ZTDD2/BRPc4G5WaI
RUDK8dm6Pgjf86N9ZxBYAnmjLl7F6lSjVD4m1rZu4lyDTU2gcYVUIgiLcPKvmFDs
slVfSADA1w7+MDxjXzL681v/Bssqk87zFUKqoykpUF7lf5EVu7mYl1+/Lsni4qIJ
mA813s3MpCBxg+PcusCQsV1oqsLgIjNRKWF9h49s5sCqaTLBW0coj6zlUp8DcwPD
juh7qWTvSwUcYnbSQokm4v+iLvozJzOBYFiiLpA+KeD2PafZZt+Zc6bMsJ0TJt9z
rOU7Ee8t+djKjJpEGW6aaX6RgjPXleWd97dnl1xJr4cj7F6b6NyE430dB7KVIUUw
jHqLdFESExXYy6grTsMN
=nVmu
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Sent, transaction id 7e3b804a886820263c301533019942529d0aeddd48659eabad076eff8d6562ea
Please repay 0.0055 BTC to bc1qtfv0rgqhz8jfzcy5cve6y4z9nhv8n52r9w86aa
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEvCux02EEk5vpJKpRoJ5kP1QcD8UFAlrE2GIACgkQoJ5kP1Qc
D8W1ZQ/+Oc8dv4LhkNPqf4BZX8WnKBAqEYDtwdSYmu15D7+aKF+fQKHEpN/fPPNb
PwJb/o5Hek0PEfXZcJ87O7HWenkZzdV51yGmbRYVg909OoKKNi/vL3pdjhpyOD2m
de38D8aUdt8aiDB4qNScC7NVPjuXY2E9bZO14t6bomdNf7Ee2ZJAPCuntY6ePrnZ
oXPKmVa0TxUPRT9KkCoiXJ+ShafNKPqjMhQtLXFHz9IWGmI+iKfnyjJb/Vur0Jbu
iRo5N5Gki6SwIAgzEJKXRhxSb85xbfIolMsbpq+wJncCsFRLa0+P5YEQQ0pWZ06Q
P/WrqwQG2XYy2ZRqgUUc0QrgLw3rlDx/RJJP0sysUachkfscPXZGGEZpTd9rRuaE
0nu+ltuCa5/40e218xuFydCoRM669jnaLG5GJ7iN3L9wJc7YqElleftGwtZn5P2I
7bA3LfFhTMNm6TN8MVD7EuRYdxzQr9ZwFukjuuz5PPMRdQ0xcxCbzav14hizikCE
uUgXbIgEgJoWIIxzNX8n7PxPGSrioWf/gOuzswEmplj7vijRQQa31qUO2TTU1EIu
n1y4idwmnNXcHT12LshEJnFBAmtXpz0pUdREcT/qakRY1BuangAuJvsutEwQubPQ
kL3isW2eaokzeR2m+7GUXHHD2RDtPP6yRFXPSpR64N7VZE6WA/E=
=x5IN
-----END PGP SIGNATURE-----
Sorry for the delay, also feel free to use the full loan duration this time  -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
This is Sellingaccs (u=1831676) requesting additional 0.0042 BTC with repayment amount being 0.0047.
The payment date would be by 17.04, or as soon as i receive my paycheck.
Address: 3ACcSBSDAoYK1MJHK6vku2YFyVk3FNYQ4c
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJayIwZAAoJEKkgyZcwTnV4WgYP/1LeafPCuPbkDd1foXl4xdcA
qThwwkDV6dF1mBNQeCvRC+VY0vKTjz2G2NXA5khW6aoLt00kDootdsfRUAT79rtv
OJKNRXzXwezJs7dWq/rm06XtyRB90o8ovAMLwEP58oTIf00fFGm4PUcZWjcpybG3
sq6AKLXLGrQSx5n67v7RAxiOuGuVfw0WfrBJWlTNcyErsaJaab9/hGZZSFCwLKJD
IjuQzUXww/ga2c5GDRpwynwez0OUHrEJV9ULnE3sZMPiXaIrq4qneaN/RvqYy3BJ
9irhaJcl9H7d+fIylo1DglYB5xq0ZNmNjsIhO2Z56ZayUVAQF3YiV1m+Wp0EG0rQ
Crs7CiicG2sk5pTkqun3p+mxpj6g9xJR381sMEXZT+T53OeoNLWNXvFu1BJHATSJ
TtrevTpi0JwRiDKqZ1WjvswGKUL58kSuxxjHbf1oDlj0biZLJpHKQ17XEHhcnhHo
D3r8BNJNFMzYcpNv+qMUqzG/x1o28RtWFTCmvve903lXQImWdZyK69EprMY4yC4x
6jsyp7pJcsosS+seoOECrD85nJMur3s6lwIx4U4jiFiZ5eZIS/jBiiWVckLe8hMb
eFaEP+7YWeIpWGVSmsSYneUU5lycPnQYQphC7uDLwS0NnDK3Uqlu6cC/392VQHM3
FI58br8h/caNXTyah0p9
=c4D0
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Sent extra. d1377fa7a2b534f3d731be3bec185c036b950ed315a56368951da42d95c84cdf
Please repay 0.0102 BTC to bc1qtfv0rgqhz8jfzcy5cve6y4z9nhv8n52r9w86aa
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEvCux02EEk5vpJKpRoJ5kP1QcD8UFAlrInmcACgkQoJ5kP1Qc
D8WNiA/8CDNtg1kVIIdW3yEl+kPYwl7+T0rZzSFCqAKnF7Hgbw5ksyKrOFzhAEub
DwPvaeva80BGqm0wAb+xYUU6wACvomgMc4hIPH3wq/HfkCdO3EUY2y0DNP8CQRCo
RfZ6f1JzvGVfXjF3hV8EiGta6UwcTAScXuQeJ7aY/570iGCUOxtvug9NbuBaX1Se
Xi7lz7DYuVCvTszvhOmdb3Oh11LwSUlp+ACFVlqV5QYQy3x9KaRjlzAGILpePwQb
HbrmBkSJ01pkx0wAwDoA1vX0vxMAqN+7sctE9Eoi8G0wCa5IKSOG6DqvePQvhnbK
MGgrk2Fx/o81osBTS+kOZfZ3xqLmAJCMOzmuC7k2n4mLg+xZY2QmmnSMyfeOKXcl
iVbWYpRv8Tb/K6FqGQa/S75grvGwr/Sh5To2KOuTah+uihrn+65uCTFcH3rrE+Qt
kd28WIx32MkEBa7Vzclt8z7OX0L7fDCA/mlBA2l422sJlIpbVsfmWUP0ZozbZScW
3rLqkT7mGi6L9VPdeMZCHvcGkRk9dKVr1dS8h8DN3VhkC0fbwfzkAM67dj/g3JJ1
M0tne9SO37mH84MKcTq0JCR1NczIBOexNFyFnbvIZ5zVp7mjmiY1vkQR2I7MEIw0
6mPO2UKXpVZQksHb12bqW2VtuVURzLxVeMhoWGe4ltZt8bq3PeE=
=Gmqv
-----END PGP SIGNATURE-----
|
|
|
|
I've had two Ryzen CPU on supportxmr.com since this morning. Around 800 h/s. The pool still shows 0.0000000000 due.
I realize I'm not some hashing powerhouse here but shouldn't there be at least some XMR due by now? Seriously the pool is carrying that figure out to ten decimal places.
SupportXMR is a PPLNS pool, so you only get paid when you find a block (and that block matures, 60 blocks later). Usually this isn't an issue because the pool finds blocks often and it only takes a couple of hours to mature, but the network is going really slow now because of the sudden drop in network hashrate. |
|
|
|
Unknown hash rate still high, so can we assume either that was something more like Javascript mining or can we assume that ASICs were able to update their algorithm too?
We won't really be able to get a good estimate for the unknown hashrate until the difficulty adjusts properly |
|
|
|
Why are the blocks taking so long? Difficulty: Retargets at every block
Difficulty is based on the time between the last 720 blocks. It will take some time to return to normal block times |
|
|
|
Happy fork network upgrade day! May everyone be blessed with great mining profitability.
whattomine.com hasn't updated their shit, I can't tell what's going on ATM!!! I'm using http://preview.moneropools.com/#/network and https://moneroexplorer.pro/| Pool | Reported hashrate before fork | Reported hashrate after fork | | SupportXMR | 51.33 MH/s | 19.75 MH/s | | Nanopool | 60.00 MH/s | 15.00 MH/s | | crypto-pool.fr | 11.73 MH/s | 00.94 MH/s | | XMRPool.net | 01.00 MH/s | 00.18 MH/s | | HashVault | 04.00 MH/s | 01.59 MH/s |
(although this could just be regular miners not being updated instead of mining ASICs leaving) |
|
|
|
|
Happy fork network upgrade day! May everyone be blessed with great mining profitability.
|
|
|
|
|
This is hilarious, I still don't know why this coin has any support at all - it is totally worthless.
|
|
|
|
It depends. If mycoind is dynamically linked, you need to make sure all of its dependencies are installed on your VPS. You can check which libraries mycoind is dynamically linked to with "ldd ./mycoind". Here's what they are for a recent version of Bitcoin Core: matt@bigrig:~$ ldd $(which bitcoind)
linux-vdso.so.1 (0x00007ffe697c4000)
libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x00007f849d6e0000)
libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x00007f849d4c7000)
libboost_program_options.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.62.0 (0x00007f849d248000)
libboost_thread.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0 (0x00007f849d020000)
libboost_chrono.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.62.0 (0x00007f849ce19000)
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f849ca34000)
libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f849c7c8000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f849c335000)
libevent_pthreads-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent_pthreads-2.0.so.5 (0x00007f849c132000)
libevent-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 (0x00007f849beea000)
libzmq.so.5 => /usr/lib/x86_64-linux-gnu/libzmq.so.5 (0x00007f849bc60000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f849b8de000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f849b5da000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f849b3c3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f849b1a6000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f849ae07000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f849abff000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f849a9fb000)
libevent_core-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent_core-2.0.so.5 (0x00007f849a7cf000)
libsodium.so.18 => /usr/lib/x86_64-linux-gnu/libsodium.so.18 (0x00007f849a569000)
libpgm-5.2.so.0 => /usr/lib/x86_64-linux-gnu/libpgm-5.2.so.0 (0x00007f849a31c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f849e0ca000)
You need to make sure that they're all the same version as the machine you built it on. If they're different distros, it's probably just easier to build it again on the VPS.
chmod +x xxxcoind
sudo mv xxxcoind/usr/bin/
if you use this way, you can use xxxcoind in any field.
I did not even know that. So any executable that is under /usr/bin will be available systemwide without needing to write the complete path?
Been a longtime user of debian and i thought that this needs some kind of alias to achieve. Edit: There should be a space between coind executable and /usr/bin path. It can be anywhere on your $PATH. Try "echo $PATH" in your shell and have a look at all the places it looks for executables. You can append other directories to $PATH and it will search in those too (you can even add . if you're feeling silly). matt@bigrig:~$ echo $PATH
/home/matt/.opam/4.06.1/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
So if I put xxxcoind in any of those directories, I'll be able to run it without typing out the full path. |
|
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Loan amount: 0.005
Loan end date: by 17.04.2018
Receiving address: 3ACcSBSDAoYK1MJHK6vku2YFyVk3FNYQ4c
Collateral: None
Hoping that you might be able to fill this. 0.0055 as payment like before.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJaxNIkAAoJEKkgyZcwTnV4azsQAJTx8cLPb4qaHKq87/fWfX+6
Q8EmERM49ycrwNJ7eXHj7YGvwJiPyU2T1wqXX49fNwIwdBkztSHGfUVank4PoWgA
LItT+UvV4Awk0+CQFGhkqWiTPYCEjhzG9b3tPollRJeXeA3/RQNTSGs/LpcHSli7
OrqJDQGleMDLaysVMH0tQsZRpPpn02tBi6iZQnLdBQp7V9/5YhSlOzoqWSUI8Z/5
XIzkoLiPFgdb3+/1nIWy2E3QEYzdJCTmGm1WAeo5vscXMs5pMdJj5VmGtq3o3oln
rUpwSIHaQQokjZ55DjSwkUDCyskgfdniMi4U9f4Sl//YYu2/ZTDD2/BRPc4G5WaI
RUDK8dm6Pgjf86N9ZxBYAnmjLl7F6lSjVD4m1rZu4lyDTU2gcYVUIgiLcPKvmFDs
slVfSADA1w7+MDxjXzL681v/Bssqk87zFUKqoykpUF7lf5EVu7mYl1+/Lsni4qIJ
mA813s3MpCBxg+PcusCQsV1oqsLgIjNRKWF9h49s5sCqaTLBW0coj6zlUp8DcwPD
juh7qWTvSwUcYnbSQokm4v+iLvozJzOBYFiiLpA+KeD2PafZZt+Zc6bMsJ0TJt9z
rOU7Ee8t+djKjJpEGW6aaX6RgjPXleWd97dnl1xJr4cj7F6b6NyE430dB7KVIUUw
jHqLdFESExXYy6grTsMN
=nVmu
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Sent, transaction id 7e3b804a886820263c301533019942529d0aeddd48659eabad076eff8d6562ea
Please repay 0.0055 BTC to bc1qtfv0rgqhz8jfzcy5cve6y4z9nhv8n52r9w86aa
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEvCux02EEk5vpJKpRoJ5kP1QcD8UFAlrE2GIACgkQoJ5kP1Qc
D8W1ZQ/+Oc8dv4LhkNPqf4BZX8WnKBAqEYDtwdSYmu15D7+aKF+fQKHEpN/fPPNb
PwJb/o5Hek0PEfXZcJ87O7HWenkZzdV51yGmbRYVg909OoKKNi/vL3pdjhpyOD2m
de38D8aUdt8aiDB4qNScC7NVPjuXY2E9bZO14t6bomdNf7Ee2ZJAPCuntY6ePrnZ
oXPKmVa0TxUPRT9KkCoiXJ+ShafNKPqjMhQtLXFHz9IWGmI+iKfnyjJb/Vur0Jbu
iRo5N5Gki6SwIAgzEJKXRhxSb85xbfIolMsbpq+wJncCsFRLa0+P5YEQQ0pWZ06Q
P/WrqwQG2XYy2ZRqgUUc0QrgLw3rlDx/RJJP0sysUachkfscPXZGGEZpTd9rRuaE
0nu+ltuCa5/40e218xuFydCoRM669jnaLG5GJ7iN3L9wJc7YqElleftGwtZn5P2I
7bA3LfFhTMNm6TN8MVD7EuRYdxzQr9ZwFukjuuz5PPMRdQ0xcxCbzav14hizikCE
uUgXbIgEgJoWIIxzNX8n7PxPGSrioWf/gOuzswEmplj7vijRQQa31qUO2TTU1EIu
n1y4idwmnNXcHT12LshEJnFBAmtXpz0pUdREcT/qakRY1BuangAuJvsutEwQubPQ
kL3isW2eaokzeR2m+7GUXHHD2RDtPP6yRFXPSpR64N7VZE6WA/E=
=x5IN
-----END PGP SIGNATURE-----
Sorry for the delay, also feel free to use the full loan duration this time |
|
|
|
Formally this is why there are mining fees and block size limits in the first place.
So those are the only official solutions for it right now.
Of course miners can always agree not to accept certain junk transactions if they wish to do so.
How do you define a junk transaction though? Surely if somebody pays the proper fee, their transaction should be as valid as any other. |
|
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Sent, transaction id 1bb8d3b266b0c01405d9e640e4314260670e3d6570aec9f7f1d65c6ef806e6b2
Please repay 0.0055 BTC to bc1q20u4qrf2ne3w93e4ekg7d69g65kwm6hplgl6x3
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEvCux02EEk5vpJKpRoJ5kP1QcD8UFAlrBBxAACgkQoJ5kP1Qc
D8USOxAAhBuwEbEeswprAeEu7P9iMnUuM3C9ChdZBd4LnqtwEJRZFFPychfRl6aE
jN6QMJlU9RMlsS+dvB5ohWF+6WXNsRc3OWdha/8K9/LWEKGlaB7tNel3EWmwK5ga
wrhAzG9o2dT1ZS4/6uMes8hEpWkx6bunY/l28fbhz3VqdP8ARK/0sAJCGN9NDMUa
m3aLtX1TVtW1iCptPVNElpVhsoM/Xd/g9TNzlRCpsmGaq1k2AiwidVYcuxH6si3x
fizyApZxPjBQaawL0Yi/FAQ0dw5DPxEdxMm6Lt/O928GwsWSSc5y+xniGiqhHOcF
2rdKDtZDChkbJXykjvJvflF/bDtffeXsncCU7KX6jUGkh9n9Knu+0TnxZ+owSXSm
jPHc21vygmlkvbV4CF6S03G4lp1CrnGT310tFEyA0dGeJeZ1fE0FJusgs2YC/FYY
EFfvhiUzC5gs828sPPHncPcngRgHsaHE9YLXEe+COXQN3OVkPg2fmOEGLTmwmduT
JsRPx1tJ23dlL1gZi2oahxEvKXhlN1Vr5p8ZF2FPsqVKWFG84OPIslOl8gCQmfKb
VC/VCpPXbfmb1mYTbcCFE5VAimR7dewd9EUyA8YEswMq78Otg7vR5Rs+z3Mjolnk
S+eqqEAGGcPQYBfws+6u3HRH3PHZW5EWZmFgrjFi56+sqhZ8Z/c=
=HM7L
-----END PGP SIGNATURE-----
I've repaid: bfe1c3090f790e34b1b8d9a3102a51c82031e4fc2b50e6fc26a65937819219c5 Thanks for your trust, will use your service in the future as well. Thanks a lot |
|
|
|
|
Show Posts
