Really guys, you have no clue what transparency and trust really is.

Talking about transmitting private keys across the internet, not disclosing who you are or in what jurisdiction you are abiding by does not inspire any confidence.

A loaded coin, or other unloaded cold storage wallet only has ANY value if the private keys are secret.

If you have made the keys, then the coins value 100% relies on your honesty.

If employees or anyone apart from yourself has ever seen any of the private keys then it relies on their honesty too, yet you are not giving details as to how the keys were treated so we do not know that.

The computer used to generate the keys, was it air-gapped Or are you not saying?

The hard disk containing the keys, you need to ensure this can never be accessed, its not enough to delete the disk, or throw it out, the data remains on the disk and can potentially be harvested. It needs to be destroyed.

Were the keys transmitted to be printed by wifi?  Was the printing device cabled or wifi?

These (at least) are all the hurdles you need to jump through, and then you need to stand up and say you have done all this and will take responsibility for the secrecy.

The point is that the ONLY value such a coin has is through your good name printed on it, and unless you have gone to some trouble to establish this showing good processes and limited spread of information, its quite worthless, a scam even if your personal intentions were good.  Its the secrecy that gives the value, not you nievely saying you have funded the coin.

Were the private keys kept under lock and key before they were applied? If anyone saw these, then the value is lost and you need to prove that no-one did. Sending them to escrow is a crazy crazy idea, the tamperproof holigram needs to be active before you send them anywhere!

Having produced and sold cold storage wallets myself (Aka Bitcoin chocolate containing randomised bitcoin cash amounts) I have some familiarity with these concepts. But the master is Mike Caldwell, and there are many online accounts where he describes the lengths he went to to ensure that the keys remained secret and that no record either accidental or purposeful was ever kept of the keys to the coins he issued.

If your coin is to have value then you need to do the same.

Loaded coins are a great gift and a wonderful idea, but they need to be done right.

I was using HBN on a 32 bit system for years but never could get it to compile on my Ubuntu system when I went 64 bit!

However, spurred on by you, I compiled it on a Ubuntu 16.04 64 bit vm and that is looking good and may be synced in 24 to 48 hrs.

Thanks for your help.

So now it coredumps :-(

*** buffer overflow detected ***: ./HoboNickels-qt terminated
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x68fce)[0xb5f64fce]
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x6b)[0xb5ffa03b]
/lib/i386-linux-gnu/libc.so.6(+0xfceca)[0xb5ff8eca]
/lib/i386-linux-gnu/libc.so.6(+0xfdf2a)[0xb5ff9f2a]
./HoboNickels-qt[0x81b42ed]
./HoboNickels-qt[0x81b4fed]
./HoboNickels-qt[0x810d803]
/usr/lib/i386-linux-gnu/libboost_thread.so.1.54.0(+0x9681)[0xb72ae681]
/lib/i386-linux-gnu/libpthread.so.0(+0x6f72)[0xb61fff72]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb5fea43e]
======= Memory map: ========
08048000-08675000 r-xp 00000000 08:01 404733     /home/mark/HoboNickels/HoboNickels-qt
08676000-0867d000 r-xp 0062d000 08:01 404733     /home/mark/HoboNickels/HoboNickels-qt
0867d000-0867f000 rwxp 00634000 08:01 404733     /home/mark/HoboNickels/HoboNickels-qt
0867f000-08682000 rwxp 00000000 00:00 0
08b2b000-8c5f0000 rwxp 00000000 00:00 0          [heap]
8c5f0000-8c5f7000 rwxp 00000000 00:00 0          [heap]
8c5f7000-8ca83000 rwxp 00000000 00:00 0          [heap]
a30d3000-a30d4000 ---p 00000000 00:00 0
a30d4000-a38d4000 rwxp 00000000 00:00 0
a38d4000-a38d5000 ---p 00000000 00:00 0
a38d5000-a40d5000 rwxp 00000000 00:00 0
a40d5000-a40d6000 ---p 00000000 00:00 0
a40d6000-a48d6000 rwxp 00000000 00:00 0
a48d6000-a48d7000 ---p 00000000 00:00 0
a48d7000-a50d7000 rwxp 00000000 00:00 0
a50d7000-a50d8000 ---p 00000000 00:00 0
a50d8000-a58d8000 rwxp 00000000 00:00 0
a58d8000-a58d9000 ---p 00000000 00:00 0
a58d9000-a60d9000 rwxp 00000000 00:00 0
a60d9000-a60da000 ---p 00000000 00:00 0
a60da000-a68da000 rwxp 00000000 00:00 0
a68da000-a68db000 ---p 00000000 00:00 0
a68db000-a70db000 rwxp 00000000 00:00 0
a70db000-a70dc000 ---p 00000000 00:00 0
a70dc000-a78dc000 rwxp 00000000 00:00 0
a78dc000-a78dd000 ---p 00000000 00:00 0
a78dd000-a80dd000 rwxp 00000000 00:00 0
a80dd000-a80de000 ---p 00000000 00:00 0
a80de000-aa571000 rwxp 00000000 00:00 0
aa571000-aa572000 ---p 00000000 00:00 0
aa572000-aad72000 rwxp 00000000 00:00 0
aad72000-aad73000 ---p 00000000 00:00 0
aad73000-ab573000 rwxp 00000000 00:00 0
ab573000-ab5c5000 r-xp 00000000 08:01 526737     /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf
ab5c5000-ab61c000 r-xp 00000000 08:01 526744     /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf
ab61c000-ab6f3000 rwxs 00000000 00:05 10485770   /SYSV00000000 (deleted)
ab6f3000-ab728000 r-xp 00000000 08:01 1710210    /usr/lib/i386-linux-gnu/libtxc_dxtn_s2tc.so.0.0.0
ab728000-ab729000 r-xp 00034000 08:01 1710210    /usr/lib/i386-linux-gnu/libtxc_dxtn_s2tc.so.0.0.0
ab729000-ab72a000 rwxp 00035000 08:01 1710210    /usr/lib/i386-linux-gnu/libtxc_dxtn_s2tc.so.0.0.0
ab72a000-ab72b000 ---p 00000000 00:00 0
ab72b000-abf2b000 rwxp 00000000 00:00 0
abf2b000-abf2c000 ---p 00000000 00:00 0
abf2c000-ac72c000 rwxp 00000000 00:00 0
ac72c000-ac74a000 r-xp 00000000 08:01 1836594    /lib/i386-linux-gnu/libtinfo.so.5.9
ac74a000-ac74b000 ---p 0001e000 08:01 1836594    /lib/i386-linux-gnu/libtinfo.so.5.9
ac74b000-ac74d000 r-xp 0001e000 08:01 1836594    /lib/i386-linux-gnu/libtinfo.so.5.9
ac74d000-ac74e000 rwxp 00020000 08:01 1836594    /lib/i386-linux-gnu/libtinfo.so.5.9
ac74e000-ac775000 r-xp 00000000 08:01 1709519    /usr/lib/i386-linux-gnu/libedit.so.2.0.47
ac775000-ac776000 ---p 00027000 08:01 1709519    /usr/lib/i386-linux-gnu/libedit.so.2.0.47
ac776000-ac777000 r-xp 00027000 08:01 1709519    /usr/lib/i386-linux-gnu/libedit.so.2.0.47
ac777000-ac778000 rwxp 00028000 08:01 1709519    /usr/lib/i386-linux-gnu/libedit.so.2.0.47
ac778000-ac77a000 rwxp 00000000 00:00 0
ac77a000-aebde000 r-xp 00000000 08:01 1709132    /usr/lib/i386-linux-gnu/libLLVM-3.8.so.1
aebde000-aedd0000 r-xp 02463000 08:01 1709132    /usr/lib/i386-linux-gnu/libLLVM-3.8.so.1
aedd0000-aedd1000 rwxp 02655000 08:01 1709132    /usr/lib/i386-linux-gnu/libLLVM-3.8.so.1
aedd1000-aedf0000 rwxp 00000000 00:00 0
aedf0000-aee06000 r-xp 00000000 08:01 1709520    /usr/lib/i386-linux-gnu/libelf-0.158.so
aee06000-aee07000 r-xp 00015000 08:01 1709520    /usr/lib/i386-linux-gnu/libelf-0.158.so
aee07000-aee08000 rwxp 00016000 08:01 1709520    /usr/lib/i386-linux-gnu/libelf-0.158.so
aee08000-af6d4000 r-xp 00000000 08:01 1710541    /usr/lib/i386-linux-gnu/dri/swrast_dri.so
af6d4000-af727000 r-xp 008cb000 08:01 1710541    /usr/lib/i386-linux-gnu/dri/swrast_dri.so
af727000-af731000 rwxp 0091e000 08:01 1710541    /usr/lib/i386-linux-gnu/dri/swrast_dri.so
af731000-af9fc000 rwxp 00000000 00:00 0
af9fc000-afa44000 r-xp 00000000 08:01 1709179    /usr/lib/i386-linux-gnu/libQt5Svg.so.5.2.1
afa44000-afa45000 r-xp 00047000 08:01 1709179    /usr/lib/i386-linux-gnu/libQt5Svg.so.5.2.1
afa45000-afa46000 rwxp 00048000 08:01 1709179    /usr/lib/i386-linux-gnu/libQt5Svg.so.5.2.1
afa46000-afa8f000 r-xp 00000000 08:01 1709867    /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2
afa8f000-afa90000 r-xp 00048000 08:01 1709867    /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2
afa90000-afa91000 rwxp 00049000 08:01 1709867    /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2
afa91000-afaa1000 rwxp 00000000 00:00 0
afaa1000-afaa2000 ---p 00000000 00:00 0
afaa2000-b02a2000 rwxp 00000000 00:00 0
b02a2000-b02a3000 ---p 00000000 00:00 0
b02a3000-b0aa3000 rwxp 00000000 00:00 0
b0aa3000-b0aa4000 ---p 00000000 00:00 0
b0aa4000-b12a4000 rwxp 00000000 00:00 0
b12a4000-b12fe000 r-xp 00000000 08:01 1709823    /usr/lib/i386-linux-gnu/libibus-1.0.so.5.0.505
b12fe000-b12ff000 r-xp 0005a000 08:01 1709823    /usr/lib/i386-linux-gnu/libibus-1.0.so.5.0.505
b12ff000-b1300000 rwxp 0005b000 08:01 1709823    /usr/lib/i386-linux-gnu/libibus-1.0.so.5.0.505
b1300000-b1335000 rwxp 00000000 00:00 0
b1335000-b1400000 ---p 00000000 00:00 0
b1417000-b141f000 r-xp 00000000 08:01 1709509    /usr/lib/i386-linux-gnu/libdrm_amdgpu.so.1.0.0
b141f000-b1420000 r-xp 00007000 08:01 1709509    /usr/lib/i386-linux-gnu/libdrm_amdgpu.so.1.0.0
b1420000-b1421000 rwxp 00008000 08:01 1709509    /usr/lib/i386-linux-gnu/libdrm_amdgpu.so.1.0.0
b1421000-b142c000 r-xp 00000000 08:01 1709515    /usr/lib/i386-linux-gnu/libdrm_radeon.so.1.0.1
b142c000-b142d000 r-xp 0000a000 08:01 1709515    /usr/lib/i386-linux-gnu/libdrm_radeon.so.1.0.1
b142d000-b142e000 rwxp 0000b000 08:01 1709515    /usr/lib/i386-linux-gnu/libdrm_radeon.so.1.0.1
b142e000-b1435000 r-xp 00000000 08:01 1709513    /usr/lib/i386-linux-gnu/libdrm_nouveau.so.2.0.0
b1435000-b1436000 r-xp 00006000 08:01 1709513    /usr/lib/i386-linux-gnu/libdrm_nouveau.so.2.0.0
b1436000-b1437000 rwxp 00007000 08:01 1709513    /usr/lib/i386-linux-gnu/libdrm_nouveau.so.2.0.0
b144d000-b144f000 rwxp 00000000 00:00 0
b144f000-b1453000 r-xp 00000000 08:01 1711845    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqsvg.so
b1453000-b1454000 ---p 00004000 08:01 1711845    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqsvg.so
b1454000-b1455000 r-xp 00004000 08:01 1711845    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqsvg.so
b1455000-b1456000 rwxp 00005000 08:01 1711845    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqsvg.so
b1456000-b14a8000 r-xp 00000000 08:01 526581     /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf
b14a8000-b14ff000 r-xp 00000000 08:01 526744     /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf
b14ff000-b1500000 ---p 00000000 00:00 0
b1500000-b1d00000 rwxp 00000000 00:00 0
b1d00000-b1d21000 rwxp 00000000 00:00 0
b1d21000-b1e00000 ---p 00000000 00:00 0
b1e00000-b1e02000 rwxp 00000000 00:00 0
b1e02000-b1e03000 rwxs 00000000 00:05 10518539   /SYSV00000000 (deleted)
b1e03000-b1e0c000 r-xp 00000000 08:01 1711844    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqjpeg.so
b1e0c000-b1e0d000 r-xp 00008000 08:01 1711844    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqjpeg.so
b1e0d000-b1e0e000 rwxp 00009000 08:01 1711844    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqjpeg.so
b1e0e000-b1e14000 r-xp 00000000 08:01 1711843    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqico.so
b1e14000-b1e15000 r-xp 00005000 08:01 1711843    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqico.so
b1e15000-b1e16000 rwxp 00006000 08:01 1711843    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqico.so
b1e16000-b1e1c000 r-xp 00000000 08:01 1711842    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqgif.so
b1e1c000-b1e1d000 r-xp 00005000 08:01 1711842    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqgif.so
b1e1d000-b1e1e000 rwxp 00006000 08:01 1711842    /usr/lib/i386-linux-gnu/qt5/plugins/imageformats/libqgif.so
b1e1e000-b1e24000 r-xp 00000000 08:01 1711433    /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so
b1e24000-b1e25000 r-xp 00005000 08:01 1711433    /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so
b1e25000-b1e26000 rwxp 00006000 08:01 1711433    /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so
b1e26000-b1e27000 r-xs 00000000 08:01 146425     /var/cache/fontconfig/c05880de57d1f5e948fdfacc138775d9-le32d4.cache-4
b1e27000-b1e2f000 r-xs 00000000 08:01 146419     /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-le32d4.cache-4
b1e2f000-b1e33000 r-xs 00000000 08:01 146405     /var/cache/fontconfig/2cd17615ca594fa2959ae173292e504c-le32d4.cache-4
b1e33000-b1e34000 r-xs 00000000 08:01 146435     /var/cache/fontconfig/e7071f4a29fa870f4323321c154eba04-le32d4.cache-4
b1e34000-b1e35000 r-xs 00000000 08:01 146402     /var/cache/fontconfig/0d8c3b2ac0904cb8a57a757ad11a4a08-le32d4.cache-4
b1e35000-b1e3a000 r-xs 00000000 08:01 146422     /var/cache/fontconfig/a755afe4a08bf5b97852ceb7400b47bc-le32d4.cache-4
b1e3a000-b1e49000 r-xs 00000000 08:01 146400     /var/cache/fontconfig/04aabc0a78ac019cf9454389977116d2-le32d4.cache-4
b1e49000-b1e4a000 r-xs 00000000 08:01 146404     /var/cache/fontconfig/1ac9eb803944fde146138c791f5cc56a-le32d4.cache-4
b1e4a000-b1e4d000 r-xs 00000000 08:01 146408     /var/cache/fontconfig/385c0604a188198f04d133e54aba7fe7-le32d4.cache-4
b1e4d000-b1e4e000 r-xs 00000000 08:01 146432     /var/cache/fontconfig/dc05db6664285cc2f12bf69c139ae4c3-le32d4.cache-4
b1e4e000-b1e50000 r-xs 00000000 08:01 146416     /var/cache/fontconfig/767a8244fc0220cfb567a839d0392e0b-le32d4.cache-4
b1e50000-b1e51000 r-xs 00000000 08:01 146410     /var/cache/fontconfig/4794a0821666d79190d59a36cb4f44b5-le32d4.cache-4
b1e51000-b1e55000 r-xs 00000000 08:01 146418     /var/cache/fontconfig/8801497958630a81b71ace7c5f9b32a8-le32d4.cache-4
b1e55000-b1e5a000 r-xs 00000000 08:01 146406     /var/cache/fontconfig/3047814df9a2f067bd2d96a2b9c36e5a-le32d4.cache-4
b1e5a000-b1e5b000 r-xs 00000000 08:01 146412     /var/cache/fontconfig/56cf4f4769d0f4abc89a4895d7bd3ae1-le32d4.cache-4
b1e5b000-b1e5c000 r-xs 00000000 08:01 146424     /var/cache/fontconfig/b9d506c9ac06c20b433354fa67a72993-le32d4.cache-4
b1e5c000-b1e60000 r-xs 00000000 08:01 146423     /var/cache/fontconfig/b47c4e1ecd0709278f4910c18777a504-le32d4.cache-4
b1e60000-b1e70000 r-xs 00000000 08:01 146429     /var/cache/fontconfig/d52a8644073d54c13679302ca1180695-le32d4.cache-4
b1e70000-b1e77000 r-xs 00000000 08:01 146409     /var/cache/fontconfig/3f7329c5293ffd510edef78f73874cfd-le32d4.cache-4
b1e77000-b1e78000 ---p 00000000 00:00 0
b1e78000-b2678000 rwxp 00000000 00:00 0
b2678000-b2691000 r-xp 00000000 08:01 1711197    /usr/lib/i386-linux-gnu/gio/modules/libgioremote-volume-monitor.so
b2691000-b2692000 ---p 00019000 08:01 1711197    /usr/lib/i386-linux-gnu/gio/modules/libgioremote-volume-monitor.so
b2692000-b2693000 r-xp 00019000 08:01 1711197    /usr/lib/i386-linux-gnu/gio/modules/libgioremote-volume-monitor.so
b2693000-b2694000 rwxp 0001a000 08:01 1711197    /usr/lib/i386-linux-gnu/gio/modules/libgioremote-volume-monitor.so
b2694000-b26ab000 r-xp 00000000 08:01 1836512    /lib/i386-linux-gnu/libnih.so.1.0.0
b26ab000-b26ac000 r-xp 00016000 08:01 1836512    /lib/i386-linux-gnu/libnih.so.1.0.0
b26ac000-b26ad000 rwxp 00017000 08:01 1836512    /lib/i386-linux-gnu/libnih.so.1.0.0
b26ad000-b26c9000 r-xp 00000000 08:01 1836453    /lib/i386-linux-gnu/libcgmanager.so.0.0.0
b26c9000-b26ca000 r-xp 0001b000 08:01 1836453    /lib/i386-linux-gnu/libcgmanager.so.0.0.0
b26ca000-b26cb000 rwxp 0001c000 08:01 1836453    /lib/i386-linux-gnu/libcgmanager.so.0.0.0
b26cb000-b26dc000 r-xp 00000000 08:01 1836466    /lib/i386-linux-gnu/libudev.so.1.3.5
b26dc000-b26dd000 r-xp 00010000 08:01 1836466    /lib/i386-linux-gnu/libudev.so.1.3.5
b26dd000-b26de000 rwxp 00011000 08:01 1836466    /lib/i386-linux-gnu/libudev.so.1.3.5
b26de000-b26e1000 r-xs 00000000 08:01 146430     /var/cache/fontconfig/d589a48862398ed80a3d6066f4f56f4c-le32d4.cache-4
b26e1000-b26e4000 r-xs 00000000 08:01 131992     /var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le32d4.cache-4
b26e4000-b26f4000 r-xp 00000000 08:01 1711848    /usr/lib/i386-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
b26f4000-b26f5000 r-xp 0000f000 08:01 1711848    /usr/lib/i386-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
b26f5000-b26f6000 rwxp 00010000 08:01 1711848    /usr/lib/i386-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
b26f6000-b2728000 r-xp 00000000 08:01 1711497    /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
b2728000-b272a000 r-xp 00032000 08:01 1711497    /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
b272a000-b272b000 rwxp 00034000 08:01 1711497    /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
b272b000-b275b000 r-xp 00000000 08:01 1711198    /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
b275b000-b275c000 r-xp 0002f000 08:01 1711198    /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
b275c000-b275d000 rwxp 00030000 08:01 1711198    /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
b275d000-b279d000 r-xp 00000000 08:01 138804     /usr/share/glib-2.0/schemas/gschemas.compiled
b279d000-b27a4000 r-xp 00000000 08:01 1709984    /usr/lib/i386-linux-gnu/libogg.so.0.8.1
b27a4000-b27a5000 r-xp 00006000 08:01 1709984    /usr/lib/i386-linux-gnu/libogg.so.0.8.1
b27a5000-b27a6000 rwxp 00007000 08:01 1709984    /usr/lib/i386-linux-gnu/libogg.so.0.8.1
b27a6000-b27cf000 r-xp 00000000 08:01 1710255    /usr/lib/i386-linux-gnu/libvorbis.so.0.4.5Aborted (core dumped)


Any one any ideas?
There is no infor in and debug.log or db.log

I am not sure this is going to work.

The client has come up a mere 270 days begind, this is good news. There is only 1 peer which is odd but network traffic is ongoing.

But I am getting thousands of messages:

ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed

in the log file, 10 or 20 a second, so I think that the client cannot read the block chain files.

This is running under ubuntu 14.04, a 32 bit virtual machine, and I seem to recall a possible difference in leveldb file formats.

(Wish I could find a version of the client that compiles or runs under ubuntu 18.04 64 bit but thats another issue.)

Oh, now something different
2020-04-20 10:42:37 socket error accept failed: 24

Ah, I know this one.
ulimit -n
gives 1024, this is the max files the system can open and its not enough.

ulimit -n 16000
ulimit -n
16000

Then run the client in the same window, maybe that will work...

[Edit.. wrongly typed uname when i meant ulimit]

Thanks Downloading now.

Can anyone point me to a blockchain download or torrent source? I have to download the complete blockchain and its taking ages, in spite of having plenty of connections?

Hi,

I am a subscriber and its a great service, but its pretty difficult to ask questions or get a response from you.

There is no email on the site.

There is a contact page, but (on my pc anyway) the recapacha does not display properly so it is not possible to submit anything to the page.

Not only that but the page forces silly choices like "I have paid but my account doesn't work" - its much better just to let people explain!

Apart from reporting the recacha problem above I have 2 questions.

1) I just brought a 3 month subscription. Before I paid I had 2 days left of my old subscription.
Now after paying it says 2 months, 29 days, 22 hours 50 min, it should say 3 Months 2 days etc, you should add on the old time remaining!

If you don't do this you encorage everyone to renew at the last moment, then people will quite rightly complain of a gap in the service!

2) I notice the history and trades are generally accurate, but there are some exceptions. I think I succeeded in posting this to you before. The symptom is that
some signals show no change in price after the buy signal for several hours and are then sold with minimal change in price (which comes out as a small loss or gain) but in fact the coin price appears disconnected from reality and the price has dropped resulting in a substantial loss. This only occurs on a few coins. These substantial losses

Please keep up the good service!

I wanted to ask about Bisq. 

Bisq is an open source platform that enables P2P asset exchange, as far as I know they do not currently list HBN, but they do clearly state the methods and requirements for asset listing.  They state that that if you commit the code and tests to list a new coin as a single commit, then they will accept this unless its controversial. There are a few other requirements, but its clear HBN complies with those already.  (Need a block explorer, must not be an ICO, ticker must not clash with other coins, etc.) A downside is that all assets must be exchanged against Bitcoin, but we could live with that I think.

I don't think this would be hard to do. Of course a p2p exchange is not as slick to use as a mainstream exchange, but its a good deal more secure since assets remain under owner control at all times. (Well, nearly, as far as I can see).

I'd like to know if anyone has tried this already, and if anyone thinks this is a good idea?

I feel that we should be exploring other exchange options as well, and wonder if there are other ideas floating around.

I am at my wits end and dont know what to do next. After some thought I have decided to open a new ticket since you do not seem to reply to my older tickets. This ticket is different in that
a) I shall post this in the PIVX forums and Bitcoin talk along with any replies you make
b) It aims to be a full statement of the problem.

The Problem:

Yobit is a small exchange that I have used for years and has always seemed reliable and honest. Recently I have come to challenge that view because the PIVX wallet is in maintenance mode and has been for 3 Months or so. I have currency that I want to remove from the exchange but its not happening.  The wallet is in maintence mode. If you fill in a request for withdrawal which you can do in any case, this message appears on screen:

  Withdrawal for such currency is temporary off.

Well that would be ok, except that its 3 months its been like that.

So I placed a support ticket and politely asked when withdrawals would be reinstated, this was the response, within half an hour:

Deposit\Withdrawal coin will be available after you upgrade the source code of the wallet. Unfortunately the developers are in no hurry to send you updates
- therefore, in order to avoid the loss of users, the network is not available.
If you have updated the source code of the coin, send us (https://yobit.net/en/maintenance_request/ Free)and we will promptly correct the problem on the coin.
Thank you for contacted the support.

So I went to the URL and submitted a free request. The top of the page states:

coin (SourceCode Update/Hardfork/Swap) with High Priority you can fill out the form below.
Payment method: YobiCode
Maintenance type:
• Free (8-14 business days) - 0 btc
• Premium (5-7 business days) - 0.2 btc
• Exclusive (2-4 business days) - 0.5 btc


So I requested a free request on 2017-11-27 expecting that this would be serviced within 18 days which is about now. I have commented a few times but never had another reply.

So is Yobit legit? that seems to be the key question now. The RIGHT way to stop trading a currency is to suspend trading, then give a reasonable time for withdrawals and then take it off the site. None of this has happened. Please Yobit, restore my faith and others in your good name and do the right thing!

Please upgrade the wallet so that me and others can withdraw the funds that belong to us. That is the only honest and decent thing to do.

(New Ticket on Yobit 10 Minutes ago.)

Yes, that worked, thank you. ! Its re-downloading the wallet, but that happens sometime!

So I'm trying to run Hobonickels 2.0.1.0 on my 32 Bit Ubuntu 16.04.3 with the Gbome desktop. I am running kernel 4.4.0-96-generic.

I have tried several approaches with no success, so in the end I thought I would document the most promising here with the problems.

Essentially I have followed the instructions in the documentation.

Building the daemon - 1 problem:

cd src/
make -f makefile.unix

rpcrawtransaction.cpp:212:77:   required from here
/usr/include/boost/variant/get.hpp:178:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false>’
     BOOST_STATIC_ASSERT_MSG(

I made this change to fix that:
rpcrawtransaction.cpp:212

// const CScriptID& hash = boost::get<const CScriptID&>(address);
                const CScriptID& hash = boost::get<CScriptID>(address);


Then

make -f makefile.unix

ls -l hobonickelsd
-rwxrwxr-x  1 mark mark 60953960 Nov  1 10:49 hobonickelsd

When run it comes up with a database corruption error but I'll worry about that later.


Now to make the qt version. I've assumed that qt5 is what should be used but some of the errormessages imply it has not been well converted from qt4


Running qmake, Its not clear to me which qt version I should be using, Some of the error messages imply it should be 5 but the dependencies list implies 5 so I went with that. The fact that the readme-qt.rst states to install qt5-default is the decider.

   apt-get install qt5-default qt5-qmake qtbase5-dev-tools qttools5-dev-tools \
        build-essential libboost-dev libboost-system-dev \
        libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev \
        libssl-dev libdb++-dev libminiupnpc-dev

0 to upgrade, 0 to newly install, 0 to remove and 10 not to upgrade.


which qmake
/usr/bin/qmake

ls -l /usr/bin/qmake
lrwxrwxrwx 1 root root 9 Dec  9  2015 /usr/bin/qmake -> qtchooser
which qtchooser
/usr/bin/qtchooser
qmake
Project MESSAGE: Building with UPNP support
Project MESSAGE: Building with DBUS (Freedesktop notifications) support
Project MESSAGE: Building with LevelDB
Warning: ignoring <defaultcodec> element
Warning: ignoring <defaultcodec> element
Warning: ignoring <defaultcodec> element
makecd /home/mark/src/HoboNickels-2.0.1.0/src/leveldb && CC=gcc CXX=g++ make OPT="-pipe -fstack-protector-all --param ssp-buffer-size=1 -O2" libleveldb.a libmemenv.a
make[1]: Entering directory '/home/mark/src/HoboNickels-2.0.1.0/src/leveldb'
make[1]: *** No rule to make target 'libleveldb.a'. Stop.
make[1]: Leaving directory '/home/mark/src/HoboNickels-2.0.1.0/src/leveldb'
Makefile:723: recipe for target '/home/mark/src/HoboNickels-2.0.1.0/src/leveldb/libleveldb.a' failed
make: *** [/home/mark/src/HoboNickels-2.0.1.0/src/leveldb/libleveldb.a] Error 2

find . -name libleveldb.a
./src/leveldb/out-static/libleveldb.a

Hmm,
Well, copy that file up and see what happens::
cp ./src/leveldb/out-static/libleveldb.a ./src/leveldb/libleveldb.a
Didnt help. removed the copy.

So thats where I am at the moment.

Anyone any advice ?

JollyGood - useful information - but what to do next. I have lost a substantial amount to this outfit. Looks like its been going the best part of a year. Any course of action sugested?
 

Please add bitcoinat.co.uk - They take your money then ask for more !! 

So I have just been scammed, and not by a trivial amount either. This site, which has been operating for at least a month. Its obvious with hindsight that I could easily have protected myself if I had done the most trivial amount of due dillegence, but I sent 100 ETH to this it in a single transaction, and now I pretty much regard it as lost. 

Please do not tell me how stupid I have been, I am aware of that! Of course I should have known better, but a moment of stupidity is all it takes. I am gutted, of course.

If you have any idea how I might recover something, anything, I will give you 25% of whatever is recovered. Let me know, give me an insight by PM of what you think should be done. If I agree, I will give you further information and ask you to proceed. There are a few emails. I have remained polite. I have also filed a police report but thats pretty hopeless I dont expect anything from that. I am thinking along the lines of scamming the scammer but really I dont have the litrary skills to do that. Perhaps you do.

The website lists a postal address which it turns out is rented office PO boxes. Their PA refuses to say if they know of bitcoinat. There is no such registered company in the Uk.  The email headers imply a los angeles address and I have also been told there may be a Austria connection (Virwox).

Really this is aweful and very very hard to accept, extremely depressing.

On a more posative note, whats the best way to take the site down to prevent others falling for it ?

This website is STILL active, and still scamming.  Can we not get it taken down?

I Am really fed up. I brought AUR at BTER exchange but they seem unable to send it to me.

I really suggest NOT sending money or BTC to this exchange.

These are some of the dialogues I have had:

Lates from me, just now:
So let me get this straight. Its impossible for me to withdraw my 3,619.965682     AUR because your withdrawal process is broken. You cancelled my withdrawal "so that I might use it". But I cannot sell AUR on your exchange at the moment because you have orders for about 15AUR if I understand.  Is this correct?

Please either give me my AUR or refund the BTC I paid for these AUR which I think is 0.5 BTC near enough. This is just a scam, its been weeks.  And please do not keep closing my tickets, this ticket is closed when I have my funds returned to me and not before.
Mark.

Your request (25387) has been solved. To reopen this request, reply to this email.

Bter Suppo    
Bter Support (bter)
Mar 10, 15:47
It was cancelled so that you might use it.

Mar 10, 04:46
This is still processing, after some 12 hours. This is really not acceptable. Please explain what is going on.
Really wondering if I will ever get my funds back.
Mark


I have done this.

How long do you think it will take this time?

If I buy AUR in the future will there be a problem or did you have a problem in the past which is now fixed?

Please, some explanation of what has happened would really help.

Mark.

On 09/03/16 09:09, mark wrote:
> Ok will do.
>
> But some explanation would be nice.

BTER Support: Mar 9, 17:03 You may try again
Mark Winder4: Mar 9, 04:05
In request 25282 you say my witdrawal was cancelled, but you should either cancel the transaction and refund my bitcoin, or allow me to withdraw my AUR.
Why is it cancelled? If you cannot withdraw then I want my Bitcoin back.
You have never at any stage offered any explanation for this. Why do you allow people to buy AUR if you cannot withdraw?
This email is a service from bter.

> pheew i though money was stolen from another exchange what would have caused price bumpings you should change the thread name
I dont know about price bumpings, but its always a sad day when people get money stolen by scumbags.
Thing is, if I had had any money on there, it would have been. I have no doubt that in a matter of days many people will have had their money stolen from BTC-E if this attack vector is a general one, and I have
no reason to think it isn't hence a post here.

No, the email was (apparently) from no_reply@btc-e.com.

I have just received a message saying successful authorisation to my Btce account from the ip address 109.201.137.162 which apparently is based in the netherlands.
This was timed at at 26.06.15 21:43.  according to the message, it was 19.43 here so presumably this had just happened. 

As I did not log in, it looks like the account has been hacked or brute forced. For me I dont think there are any implications, its an old account - I tried to log in
and change my password but they had already done that I was not fast enough.

The message from btce is from a noreply address (That really is so smart isn't it!) so I have no idea who I should tell.

That's pretty annoying, but if you have funds on Btce, beware.

Mark.

Thank you, that worked like a charm, and took a lot less than an hour!

Your points about the notice that was given are well taken: I was speaking from a position of fear and worry!!

regards,


      Mark.