Is there currently no active developer for mooncoin? I was just curious ...
|
|
|
I clicked on the reddit link to find this, just for shits-and-giggles. OP delivered said shits-and-giggles.
I find it so laughable that these coins plaster a giant "CoinSource Trust Verified" on all their announcement pages. Like that means something. ProTip: CS is a paid service that fleeces you for your btc, while providing absolutely no legitimacy whatsoever.
1 year and slow/no development and little interest. Why should we care about this coin?
|
|
|
btw, this was the error I got when it crashed last nite after completing sync:
EXCEPTION: St11logic_error basic_string::_S_construct null not valid bitcredit in Runaway exception
bitcredit-qt: ./allocators.h:47: LockedPageManagerBase<Locker>::~LockedPageManagerBase() [with Locker = MemoryPageLocker]: Assertion `this->GetLockedPageCount() == 0' failed. Aborted
|
|
|
I finally got a Debian build to complete, worked fine until the sync completed but now crashes with a segmentation fault on startup.
I will review the code a bit more this weekend if I have time. Nice changes from what I see though. Good luck guys.
Good to know. Make sure you are using the latest build If you aren't sure, just do a git pull. I did do a git pull, just to be safe. I glanced at my debug log but found nothing helpful there. Not sure why this has been such a headache for me. I will try to strip the executables and run them from my Ubuntu VPS and see if I notice any differences. I really do want this to work on Debian 8 though, as I have a spare box begging for a project like banknode.
|
|
|
I finally got a Debian build to complete, worked fine until the sync completed but now crashes with a segmentation fault on startup.
I will review the code a bit more this weekend if I have time. Nice changes from what I see though. Good luck guys.
|
|
|
@teamfresh I've decided to take a break for a bit. Love the chat, but one of your mods in particular is gaming points by posting nonsense all day. Personally tried to be diplomatic about it with them (and remind them of the numerous examples of bans handed out for this) to no avail. Hope you can fix this upon your return, as easybitco is a nice discussion site, without ref links and text walls all day. Good luck and hope to return soon! I agree with this statement. Starting today I will try my best to enforce the "no referral links unless asked for" rule, as well as a max. 3 consecutive posts per without replies from others. Good to hear, I will pop back in this morning. I certainly don't want to rain on anyone's parade, and we are all earning at different levels but this situation had gotten out of hand, being told I was making up rules on the fly AFAIK, those have always been the simple rules for easybitco and CoinVisitor before that. I documented all before I left yesterday and recommended that user be removed as mod, though it is in teamfresh' hands.
|
|
|
Debian 8 on all home PC's, Android/Arch on the ARM devices.
|
|
|
Hello, I want to run some nodes in Middle Europe, but feature --disable-wallet don't works with latest source ( https://github.com/unobtanium-official/Unobtanium) I tried it with many kernels 3.10+ and other needed libraries versions compilling error: libbitcoin_server.a(libbitcoin_server_a-rpcmining.o): In function `getauxblock(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::string> >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::string> > > > const&, bool)': /root/cryptocoins/Unobtanium/Unobtanium/src/rpcmining.cpp:670: undefined reference to `pwalletMain' libbitcoin_server.a(libbitcoin_server_a-rpcmining.o): In function `CReserveKey::~CReserveKey()': /root/cryptocoins/Unobtanium/Unobtanium/src/wallet.h:781: undefined reference to `CReserveKey::ReturnKey()' libbitcoin_common.a(libbitcoin_common_a-auxpow.o): In function `GetAuxpowMiningKey()': /root/cryptocoins/Unobtanium/Unobtanium/src/auxpow.cpp:129: undefined reference to `pwalletMain' /root/cryptocoins/Unobtanium/Unobtanium/src/auxpow.cpp:131: undefined reference to `CReserveKey::GetReservedKey(CPubKey&)' libbitcoin_common.a(libbitcoin_common_a-auxpow.o): In function `~CReserveKey': /root/cryptocoins/Unobtanium/Unobtanium/src/wallet.h:781: undefined reference to `CReserveKey::ReturnKey()' /root/cryptocoins/Unobtanium/Unobtanium/src/wallet.h:781: undefined reference to `CReserveKey::ReturnKey()' collect2: error: ld returned 1 exit status make[2]: *** [unobtaniumd] Error 1 make[2]: Leaving directory `/root/cryptocoins/Unobtanium/Unobtanium/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/cryptocoins/Unobtanium/Unobtanium/src' make: *** [all-recursive] Error 1 I am going to attempt to duplicate this error, give me a few hours to spin up a VM and I will report back. Also, please ensure you are defining relative paths for EVERYTHING in this build. I was unable to compile without specifically defining the location of boost libraries.
|
|
|
I know things are serious around here right now, but in other news... I've identified POTATO MAN!!! Latvian UNO market doing well?
|
|
|
So it required a slight code change. If one isn't comfortable making a quick code fix, then one shouldn't operate a pool. Small price to pay IMO.
|
|
|
I was trying to build a Uno wallet on Ubuntu yesterday, but failed. Would be very cool Siameze if you (or someone) would write a step-by-step instruction, or a script of some sort, that would grab everything, install it and compile. I found a BCT thread that had scripts for many different coins, and I tried to modify for Uno, but didn't succeed on my first try. I'd love to be one of the elite here who could do what you just taught yourself to do. I will be glad to write a general guide, though I can tell you from many years experience that their unfortunately isn't a one-size-fits-all solution in a lot of cases, depending on your distro. My issue turned out to be an obscure boost/libx issue I only sorted from hours of poring over the updated code. On Ubuntu, it should be a pretty simple matter. If you shoot me a PM with your Ubuntu version and the error you have, I will be happy to help. Trust me, it is best to learn the build steps, even if you fail at first, because you will gain a lot of knowledge that helps in future builds.
|
|
|
Okay, that is a bit better, but I really think there should be a standard procedure to create these binaries. There should be one, max two persons in charge, who use a verfied build environment to create those win/mac binaries and then publish them on the offical page along with some checksums to verify the file integrity.
We are dealing with some kind of money here, so just asking people to ask other people to compile a binary, and then publish it as the "official" one, is a really, really bad idea. I do not want to imagine what would happen if an attacker manages to sneak in his binary.
Knowing this, I now have to use wallets that I have compiled myself, which is somewhat annoying.
I get and appreciate your security concerns. Nobody is in charge of anything here. If you see something that needs doing, feel free to do it. You can even be in charge if you like. Nobody is forcing you to compile wallets. Sit tight. It's getting done. Do you have to move around coins every day? If not, chill. But yeah, your security message is well received and appreciated. Now, since your wallet is compiled, send Falling Knife a nice kilo of UNO for being a dick to him. He does this for free. I assure you I have had many discussions with IMZ in regards to security. A lot of people are blissfully unaware of such things, and yes education is important. However Gekko has a valid point, if you want something done securely there is no better person to do it than yourself! That is why I spent the better part of 3 days working on a build for 64-bit Debian. Sure I could wait for a binary, or rant about the lack thereof. But in my short time with the UNO community I have learned if you are looking for a super fast paced environment, you are in the wrong place. I also appreciate all that helped me with my issues.
|
|
|
This may or may not be a great idea, but I am personally so tired if all the NuTeam spam in the cryptocurrency section of reddit, just the mention of anything NU related I immediately dismiss.
We do have a rather zealous community member who posts a lot of things there, I wouldn't let that sour your opinion of Nu overall. Are you talking about Crypto_Coiner? Maybe we should ask him if he could slow down on the postings. Honestly, I think only major news should be posted there. NuShares for NuBits burning, opening of liquidity pools, B&C exchange announcement, etc... Sometimes I see him posting random threads that don't really seem to be that important. That would actually be excellent. I have no issues with the Nu community overall, but lets just say that overposting there is what killed reddcoin in the eyes of many. I enjoy reading about interesting updates and milestones for any cryptocurrency, but if I want daily updates I'll subscribe to r/NuBits. I wish you all luck in your project.
|
|
|
I am also pleased to announce that after tearing my hair out for 3 days, I have fixed my build issues on linux. Longest damned wallet build of my life, but I am happy to be back in the game with UNO.
|
|
|
@teamfresh I've decided to take a break for a bit. Love the chat, but one of your mods in particular is gaming points by posting nonsense all day. Personally tried to be diplomatic about it with them (and remind them of the numerous examples of bans handed out for this) to no avail. Hope you can fix this upon your return, as easybitco is a nice discussion site, without ref links and text walls all day. Good luck and hope to return soon!
|
|
|
4. Hacker addresses will not get bonuses. Also a hacker will not be able to spend stolen coins on Moon Marketplace that is assumed to be launched in June and will allow to buy for Mooncoins on a lot of marketplaces including Amazon (via gift cards).
This is excellent news. I was unaware there was a "Moon Market" in the works. I look forward to hearing more about this.
|
|
|
This may or may not be a great idea, but I am personally so tired if all the NuTeam spam in the cryptocurrency section of reddit, just the mention of anything NU related I immediately dismiss.
|
|
|
Will it help if I reload the whole blockchain? and how do I do that?
Let me run a test and try to get back to you. In unobtaniu.conf I'll setup connect={0.10 node ip} and try to resync the blockchain. If it works I'll let you know. This is a follow up to EBK1000 regarding a workaround I tried on my Uno Windows wallet. I added only 0.10 addnodes to the Unobtanium.conf file in my Windows wallet. Based on my experience, I don't recommend this as a workaround. It's too much work, and the fix does not persist. After downloading the block chain, eventually the wallet drifted out of sync again. It did however recover coins received up to the point it synced with the 0.10 nodes. If you have a 0.10 Linux wallet, you're good. If you have Win/Mac wallet, please continue to sit tight. Sending your coins will work, but receiving them on Windows/Mac is unpredictable. They are not "lost," if you send them to a Win/Mac wallet; you could, for example import our priv keys to a Linux wallet and access them. Can I install the Linux wallet and import my wallet.dat file from Mac? or import my keys to the Linux wallet? Yes. The wallet.dat files are platform agnostic so no issues there. If anyone that has built the linux wallet could tell me what version of boost they used to do so, I would be very grateful. 1.55 isn't working for me.
|
|
|
To Developer(s): This is so unprofessional approach to upgrade that I don't even know what to say. My pool had approx 5% share in total mining and NOBODY informed me about fork. I am upgrading now but last 108 blocks mined on my pool are gone. Congratulations.
feeleep
Be glad you can upgrade. I can't even build a wallet yet, I am linux only here. This may spell the end for me in the UNO community for a while until I fix this issue.
|
|
|
|