Will be voting for Masternodecoin on Nova!
FYI, am willing to offer 200 sats per coin for anyone wishing to sell 50,000 coins.
PM me if interested.
|
|
|
Don't have any ability to mine, so anyone wishing to sell some coins (include the dev, of course... hint, hint), I'd be interested in buying some.... say 2000 or so. I know it's new so most people don't have many coins. Just saying....
|
|
|
I have a few MTNC coins... I've unlocked the wallet for staking, but after 24 hours, it still says their not staking. Any tips?
mtnc is different from other POS coin , when you set up mastenode then you can get pos and masternode reward,if not ,then nothing even you have mtnc in your wallet. Ah, so you need enough coins to set up a masternode (50,000) and have the masternode running, then you get both masternode rewards AND staking rewards? Is staking on the same coins associated with the masternode, or just extra coins?
|
|
|
I have a few MTNC coins... I've unlocked the wallet for staking, but after 24 hours, it still says their not staking. Any tips?
|
|
|
Have updated to the recent post on discord for the peers.dat and KoreCoin.conf file, but still can't sync. Currently 7 hours behind and stuck. Any more advice (on a Linux system)?
|
|
|
I just downloaded the source code to compile a version of the Masternodecoin Wallet on a Linux machine. I'm using a Linux Mint 18.2 machine, but it should be valid on any Linux machine, specifically any Ubuntu machine. I used a git clone command to download the wallet: git clone https://github.com/masternodecoin/masternodecoin.gitThis will put the source code in a directory called masternodecoin directly in the directory that you execute the command from. Two things you will need to do before executing the commands to make the coin: $chmod 755 src/leveldb/build_detect_platform $chmod 755 src/secp256k1/autogen.sh Once you have executed the above commands, you can then continue with the make: $qmake $make This will create the Masternodecoin-qt executable in the main directory. There you have it! Now you have a Linux qt wallet for Masternode coin. nice guide . it should compile leveldb and secp256k1 first Thanks... participating in the second Airdrop, but know I'll need additional coins for a masternode. Do you know what the first exchange will be to list the coin? Would love to be able to pick up some early... before the price rise did you already recieved masternodecoins in your wallet? , if not then please PM me your walletadress , i'll send you a little this community grows bigger everyday and you helped a lot of people Thanks, glad to be of help to anyone. I'd also be happy to help anyone who has problems. I also PM'd you.
|
|
|
My masternode on Linux works fine, I earn 1 8bit per day. The GETINFO command returns this message: "Errors": "EXCEPTION: St9bad_alloc \ nstd :: bad_alloc \ n8bit in ProcessMessages () \ n" what does it mean ?
It means that you should upgrade your memory, however, as long as your client accepts blocks there's nothing to worry about. I've been staking my wallet for a couple days. I noticed that ALL of the coins that come in say "generated but not accepted". What would cause this?
|
|
|
I just downloaded the source code to compile a version of the Masternodecoin Wallet on a Linux machine. I'm using a Linux Mint 18.2 machine, but it should be valid on any Linux machine, specifically any Ubuntu machine. I used a git clone command to download the wallet: git clone https://github.com/masternodecoin/masternodecoin.gitThis will put the source code in a directory called masternodecoin directly in the directory that you execute the command from. Two things you will need to do before executing the commands to make the coin: $chmod 755 src/leveldb/build_detect_platform $chmod 755 src/secp256k1/autogen.sh Once you have executed the above commands, you can then continue with the make: $qmake $make This will create the Masternodecoin-qt executable in the main directory. There you have it! Now you have a Linux qt wallet for Masternode coin. nice guide . it should compile leveldb and secp256k1 first Thanks... participating in the second Airdrop, but know I'll need additional coins for a masternode. Do you know what the first exchange will be to list the coin? Would love to be able to pick up some early... before the price rise
|
|
|
Awesome project...hopefully the life can stay in it this time! I shall be buying more!
KORE is here to stay. We are not going anywhere unlike the majority of crypto. I have even been preparing KORE Team and Projects that if anything ever happened to me they would carry out the end goals and we have the type of Team that could do it seamlessly. MikeMike Obviously I don't know you from "Adam", but it seems like this coin has a really good team involved here. I looks like MikeMike has put a lot of time and effort (among other things) to really put Korecoin on the map. I am really looking forward to everything this coin has to offer... especially the in wallet phone and masternodes. Can't wait for all of this to be launched. Looking to pick up more coins when I have a chance. Keep going Kore Team!
|
|
|
I just downloaded the source code to compile a version of the Masternodecoin Wallet on a Linux machine. I'm using a Linux Mint 18.2 machine, but it should be valid on any Linux machine, specifically any Ubuntu machine. I used a git clone command to download the wallet: $git clone https://github.com/masternodecoin/masternodecoin.gitThis will put the source code in a directory called masternodecoin directly in the directory that you execute the command from. Two things you will need to do before executing the commands to make the coin: $chmod 755 src/leveldb/build_detect_platform $chmod 755 src/secp256k1/autogen.sh Once you have executed the above commands, you can then continue with the make: $qmake $make This will create the Masternodecoin-qt executable in the main directory. There you have it! Now you have a Linux qt wallet for Masternode coin.
|
|
|
Thanks. I saw that one but couldn't find any api info for it. Do you know if there is an api and if so where the documentation is? Looking for an api to look up balances and transactions.
|
|
|
Anyone know of a block explorer with an api?
I was using khashier.com, but it's been down for a long time.
|
|
|
There are cheaters on board who abuse not enforced MN payments. I don't know what's the scale of the problem currently, but the best way to minimize profits of cheaters, maximize profits of legitimate users (and actually improve network security ) is to run both staking- and master- nodes. When I try to run a cold/hot wallet and stake with my masternodes, it stakes the 112 coins from the masternode and screws up the masternode. Any way to avoid this?
|
|
|
It would be beneficial if there was standard api access to the block explorer like most have.
There's standard (ABE compatible) API available (coinmarketcap is fully suported). Could you give an example of say.... how to get the balance of an address? http://explorer.8-bit.ga/chain/BIT8/q/addressbalance/8ZTy8WbdpXEpkzriUpanb3bktW9A8ZvEekDo not abuse this feature by a flood of automated requests please... ie to get a current snapshot of balances of all address it's better to run a private explorer. Thanks, just writing an interface to check my own balances.
|
|
|
Hello, I have just arrived. The block explorer & website will return this evening (UTC), I am syncing my nodes finally.
That's great 8-bit-Party! It would be beneficial if there was standard api access to the block explorer like most have. There's standard (ABE compatible) API available (coinmarketcap is fully suported). Could you give an example of say.... how to get the balance of an address?
|
|
|
src/instantx.h:34:1: error: reference to ‘int64_t’ is ambiguous int64_t CreateNewLock(CTransaction tx); ^~~~~~~ ...
I get hundreds of these "int64_t is ambiguous" errors, and the build fails.
Did this issue arise for you?
Seems the only solution is to go through and append "::" to every instance of int64_t declaration in the code.
I have tried this, but screwed something up, ended up wasting hours of time. Any help much appreciated.
What's your boost version? 1.62 Build has come a lot further along, but now I get this error: $ make -f makefile.unix&&strip 8bitd&&sudo cp 8bitd /usr/bin /bin/sh ../share/genbuild.sh obj/build.h g++ -c -O2 -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -DUSE_SECP256K1 -I/home/r8st/8bit/src -I/home/r8st/8bit/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/r8st/8bit/src/leveldb/include -I/home/r8st/8bit/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/darksend.d -o obj/darksend.o darksend.cpp darksend.cpp: In member function ‘bool CDarkSendPool::IsCollateralValid(const CTransaction&)’: darksend.cpp:978:29: error: cannot convert ‘bool’ to ‘bool*’ in initialization bool* pfMissingInputs = false; ^~~~~ makefile.unix:201: recipe for target 'obj/darksend.o' failed make: *** [obj/darksend.o] Error 1 Has anyone received this error while building 8bitd, and is there a known solution? Change "bool* pfMissingInputs" to "bool fMissingInputs " in darksend.cpp line 978. On the next line change "pfMissingInputs" to "&fMissingInputs". I could have sent a patch, but I am on a touch screen right now, so... just do manually That is just a stupid programming mistake done by the first dev (not 8-bit-party). Your compiler is too clever to digest that stupidity. This code really needs to be refactored... Should we all apply this patch?
|
|
|
Looks like things are really starting to stabilize!
I have us started off on getting a listing on masternodes.pro. We would have the number 1 spot in ROI there. Only $178 more needed to get listed. Come on people, lets get this 8Bit Party started!
|
|
|
Hello, I have just arrived. The block explorer & website will return this evening (UTC), I am syncing my nodes finally.
That's great 8-bit-Party! It would be beneficial if there was standard api access to the block explorer like most have.
|
|
|
Not sure what this means exactly, but my log is constantly filling up with:
connect() to 136.243.147.46:18888 failed after select(): Connection refused connect() to 136.243.147.46:18888 failed after select(): Connection refused connect() to 136.243.147.46:18888 failed after select(): Connection refused connect() to 136.243.147.46:18888 failed after select(): Connection refused connect() to 136.243.147.46:18888 failed after select(): Connection refused
Is this someone on the wrong chain or something else wrong? If so, can we ban them or something?
|
|
|
|