Hi all, have been studying wallet segmentation faults for last few days, I have worked with Cointopay to resolve these issues. They were unable to upgrade due to this. They were waiting for Vassilis to update them on topic. ... cut ... The solution, because I actually would need to submit patches to bitcoin, since mooncoin branched from bitcoin right, would take more time to fix for future versions. So they needed to go back to 4.8, and that is actually a lot of work. Quick fix on (new) target environment: install libevent-dev install libdb4.8-dev
export CPPFLAGS="$CPPFLAGS -I/usr/local/BerkeleyDB.4.8/include/"install libdb4.8-dev libdb4.8++-dev ./configure make ./mooncoind Then after that we have a working version of mooncoin again, on 4.8 but at least working version for linux on 0.13.9-segwit. I suggested to copy the wallet.dat from their new bdb(old server) and move it to the new environment and start it up (of course using backups in the process). It worked, and now they are running on the new version.  I would recommend everyone to upgrade to the latest version 0.13.9-segwit as soon as possible, but make a backup of your wallet.dat before doing that!! as i've not been involved with mooncoin for some time; i'm not sure whether all exchanges are on new code, however.. all of my development work on 0.10.5 and 0.13 was done with libdb5.3 (aside from the windows wallet compiles) the actual issue regarding libdb4.8.30 being the 'golden standard' is related to wallet portability, as berkeley does not guarantee data integrity when migrating between the two versions; i would suggest your segfault issues lie elsewhere.. (btw, while compiling against -dev headers as you've posted; there is no need to add to CPPFLAGS as you've done) |
|
|
|
3) Discard Smart Likes and concentrate on what is important (get a new dev and a flawless wallet with proper support for the community by the dev who can answer questions like: how was it possible to move the said-to-be-"locked"-coins to the wallet of the former dev?).
locked coins did not move under my tenure; or any of the code i released. once my 0.13 release was suitably butchered; after some modifications to my forbidtx routines and transaction relaying parameters in general, the coins did indeed move. looking at the dates and actions of individuals, not sure how you've missed that. james |
|
|
|
I watched a Bits Be Trippin' vlog on YouTube a week ago, or so, and he was mining on an AI card - in place of a graphics card - and was getting 90+ MH/s on ETH. Maybe these are for the GPU market?
people who are a bit more silent on this are achieving a factor of at least 3 or 4 on that figure; but dead right, very suitable for mining.. |
|
|
|
Heading into almost a year later, still hasn't repaid me but is active here in the forums.
Hello all and good evening CryptoDatabase, To those not following; I modified the old HYPER codebase to start from a fresh chain, with longer block times. He had been sent all relevant code and binaries; and the node was running. Our final talk 4-5 days later revealed he was unhappy for whatever reason; even though the product was up and running - and he'd been sent all of coinbase. https://github.com/barrystyle/hyper2-evidence complete with intact timestamps (I thought i'd lost this, but was found a few days ago). Hope you are keeping well, barrystyle |
|
|
|
I guess we know what is supporting the price moves the last day for so. Kind of hard to go down when people can't move coins onto the exchanges to sell....lol.
Funny, I was thinking it makes it harder for the price to rise. Most people like to move coins on to and exchange, make a trade and move them off for safety. The strength of a distributed network is that it is distributed. to be honest; i'm yet to see a 'wallet in maintenance' warning for either bleutrade or coinexchange (besides the latter being dreadfully slow to use). as of five minutes ago, both sites are showing a deposit address when requested and no mention of any issues. late yesterday; i sent a small amount to bleutrade and it showed up in my account within 18 blocks (this has always been about the same for confirmations). i'm about to mine some now just to test and send to coinexchange, will let you know my results. not sure what to say, james |
|
|
|
hello james, thank you for reply
i think i have the latest wallet : Mooncoin Core versie v0.13.9.0-b257fcdsegwit (64-bit)
or can you give me a link to the latest windows version pls?
at this moment i cant compile on my pc
yep, that should be fine. i was actually yet to try Vassilis's windows wallet, usually do my dev work under debian. ran an old key of mine through it and sent it to another address. seems to work fine? the transactions that you sent (the ones not showing up correctly), were these done from the new wallet? |
|
|
|
hi james
i did the above getrawtransaction with the number and i get back :

No information available about transaction (code -5)
so i do a rescan ?
yep, easily achievable by adding -rescan to the program parameters of your mooncoin shortcut. just remember to remove it once you've rescanned, its a pain to do it a few times in a row because you didnt remove it  oke i will i do it trough command , i let you now the results, iam of to bed now its midnight here ;-) thanks james i did the rescan : now i see in transactions : not confirmed : 0/ not confirmed not in memorypool ( Status: 0/onbevestigd, niet in geheugenpoel ) did i lost my 300K here ? total of that transaction : Status: 0/onbevestigd, niet in geheugenpoel [0/ not confirmed not in memorypool] Date: 1-6-2018 11:39 to: Bleutrade deposit [here my bluetrade mooncoin deposit adress] [ not discribe here for safety if needed i wil put it here) Debet: -300 000.00000000 MOON Transactioncost: -0.01078000 MOON Netto amount: -300 000.01078000 MOON Transactie-ID: 742979eeef9719b998ee35f8687f0f3b3e77ae3f023f6919b5fdf3684e508d63 Output index: 0 sou need a little more help here to get them back or to bluetrade ;-) You put a very little transacion cost. So just wait. ah oke tel me how to change that , what i just did was to zapwallettxes and did the coins back , so tel me how to adjust the fees btw i use the recommended fees according the wallet hm, this is odd - that tx fee should be fine, regardless of fee; it will fit comfortably into the 'free' portion of a block |
|
|
|
Hi Can anyone help with stuck Mooncoin on the http://wallet.moonrush.org wallet. There is no way for me to access that site anymore. I had 1 million coins and now they are worth a decent amount to me and would really like to know if anything is possible at all to get them back. I contacted barrysty1e and had no reply as of yet. I appreciate if anyone can help me the webwallet has not been operational since september, with a warning not to use it for at least a month earlier. these virtual hosts were eventually scrapped/deleted. james |
|
|
|
theres no 'offline' for cryptocurrency, it will always remain on the chain - your ability to use it is determined by you owning the correct private key to the funds. better thought of as a lease, you never actually own it as a tangible asset; as thousands of other people running nodes would have the exact same information thats available to you. if someone else had the private key, what could you do about it? whether or not it is your 'perceived good', you only have the ability to use it through a client. |
|
|
|
The original freezing was already doubtful (that's most probably why Cryptopia removed Mooncoin from their exchange), but as said, now is a new situation, because the stolen coins are available again and are still - exactly as when they were frozen - stolen goods.
Ask your lawyer.
it's not on cryptopia, because hex and i do not like each other. having the upper hand (owning the exchange), he chose to act like a child knowing it would cause me some grief.. having just come onboard as the new dev at the time. nothing to do with the freezing; no other exchanges have had an issue either morally or legally with it. james |
|
|
|
hi james
i did the above getrawtransaction with the number and i get back :

No information available about transaction (code -5)
so i do a rescan ?
yep, easily achievable by adding -rescan to the program parameters of your mooncoin shortcut. just remember to remove it once you've rescanned, its a pain to do it a few times in a row because you didnt remove it |
|
|
|
hi james this is the transaction id : 742979eeef9719b998ee35f8687f0f3b3e77ae3f023f6919b5fdf3684e508d63
[edit] in wallet it says at transactions wallet is offline ?
ok, this generally means that the transaction wasn't broadcast, possibly due to network failure - as i can't see it in mempool at the moment. at the console: getrawtransaction 742979eeef9719b998ee35f8687f0f3b3e77ae3f023f6919b5fdf3684e508d63 (it will dump a very long hex number, copy this to clipboard) sendrawtransaction <long hex number> if you receive a tx rejected; you may have to rescan your wallet, as the funds haven't left yours. if you receive a tx decode error, you mightve accidentally put another character in the string. |
|
|
|
wel hmm got a error within the latest version mooncoin wallet :
has triggered forbiddentx alert (n=1481, txdebug=3204) in debug log ,
is this the case that my deposit mooncoin wallet is offline at bleutrade ? it can send my coins over there ?
this is the function performing normally. it actually flared up quite a bit this evening; it is dropping/preventing the transactions from entering mempool (ready to be committed to a block), if the given transaction matches one in a list of hashes. edit: it doesnt mean that its dropped a transaction you've made, it means that another node has attempted to relay a transaction to your node, but your node has dropped it from mempool. what is the transaction id for the transaction you're having issues with? james |
|
|
|
Normally stolen goods are illegal in consequence, if not returned to their rightful owners; so an expert opinion from a qualified lawyer would be a good thing indeed.
This qualified lawyer should be also a crypto expert and understand the nature of decentralised projects. In fact there is a lack of laws in this field yet. Anyway if rightful owners want to burn coins, it's quite simple and fair. Or we can discuss it for years and while we are discussing, coins could be stolen again. Better really burn them asap. Really trying to make this the last message regarding it; we could get in contact with the 'Cryptsy Cryptocurrency Administrator' (email at bottom of http://www.cryptsysettlement.com/) asking their advice; standard 2 weeks to reply, if this time lapses; burn them. Vassilis? What do you think? james |
|
|
|
the law aspect should be considered, however just diving into the technical: https://raw.githubusercontent.com/adamkrellenstein/unspendable/master/unspendable.py is a good clean written method, which contains in it doublesha and the checksumming component. adaption for mooncoin is limited to lines 67 and 68, which need to be changed to: elif network == 'mainnet':
prefix_string = '2'
prefix_bytes = b'\x03'
else: root@vault:~# python unspendable.py bazonthemooonwithabroomvsoon ('mainnet:', '2bazonthemooonwithabroomvsoojpRhqB') perhaps a phrase can be randomly selected? james |
|
|
|
Sounds weird.
I visited block explorers,
Mooncoin has 5 independent block explorers,
you can see Rich list (top addresses) in block explorers easily.
The biggest address with 62 bil is Vassilis's address with Cryptsy coins, we know already that.
I see many other OLD addresses with coins in top 25,
but I don't see 120 bil more coins on new addresses.
Though when there are price movements, coins change their owners fast, so if you mean transactions with small addresses, it's quite normal.
Usually when a price is rising a big percent of supply is changing their owners during just 24 hours, people go to exchange and sell, other buy.
So for now I don't see anything new.
We know that about 80 bil Cryptsy coins were blocked, 62 bil were sent to Vassilis, he was going to burn it,
it's not legal to spend them etc.
They have their legitimate users and these users who had lost more than 60 % of these coins already agreed to burn them, for the bright Mooncoin future.
P.S. spending coins of other people is not legal, even if it's not fiat. Make a research, and you'll see, already there are many cases with BTC and other coins. But if the community burns its own coins, for the future of MOON, it's not this case.
my apologies, after triple-checking.. the full figure appears to be closer to 90. the giveaway for most of these transactions is they look like theyve been moved around with a script. i think that burning the coins is definitely the best way forward; while it would be more satisfying to return them to the owners, this would prove a logistical nightmare, in the case of proving it - and being able to guarantee the forbidtx code would not cause hassles in the future. however a public burn would instantly reduce the marketcap/circulation; perhaps some people would take reassurance in the fact that it was a lingering problem that is now over once unspendable. however - i think we will wait for Vassilis to comment as i think we've scared him (not deliberately of course). i'm currently running the txindex'd chain through a piece of chain mapping software; and i hope to be able to put the results up in public. james |
|
|
|
is this one of the reasons Bleutrade has deposite mooincoin wallet offline ? shoudl they said so that there were been offline? i just sent alot mooncoin to stall there but that deposit adress is offline !!!
did you block my coins ? i send 300k overthere and now floating in the net !
if you read above, you'll see bleutrade is currently having issues at the moment; it is quite difficult to get onto the site. i'd contacted the exchange about 2 hours after your post, so the events are not related. james ( just for piece of mind, your address does not appear in the 'suspicious' list ) |
|
|
|
|
Hi all,
I've isolated the blocks/transactions that make up the large send, both to Vassilis_dev and to other addresses.
This was done in such a way, that the transaction to Vassillis_dev would stand out (62 billion), but the other approx 120 billion would go unnoticed (!).
The blocks in question are from 1184002 to 1184024; and have been done on an isolated stratum/node, which is given away by the coinbase address '2DupXiBoGw5VEGngUWR4quB3C3kgkTuLYJ' which was only used over a 40 minute period, and never seen again. It almost looks like the blocks were 'prebuilt' with the offending transactions in them, in an attempt to bypass the forbidtx routine (as to avoid mempool).
I've advised the exchanges to treat any transaction originating from these blocks with suspicion.
Additionally, with debugging enabled.. the forbidtx routines have been displaying fairly regularly over the past 2-3 hours.
I will keep you posted on further events,
james
|
|
|
|
Also, thank you all for your support and your faith!
It's very important for me.
i dont think there would be any bigger test of faith, for a new dev to receive 25% of the marketcap (only upwards of 15 million dollars), and then be completely transparent about it hear hear! baz |
|
|
|
|
Show Posts
