This sub-par zerocoin clone won't compile
src/growcoin/src$ make -f makefile.unix -e PIE=1 USE_UPNP=
...
g++: error: /home/coin/src/growcoin/src/leveldb/libleveldb.a: No such file or directory
g++: error: /home/coin/src/growcoin/src/leveldb/libmemenv.a: No such file or directory
before compile: cd /folder/growcoin/src/leveldb; chmod 777 build_detect_platform i also had to do this or i got compilation errors on linux: Change this:
src/qt/walletmodel.h
Line: 100
void getStakeWeightFromValue(const qint64& nTime, const qint64& nValue, quint64& nWeight);
To
void getStakeWeightFromValue(const int64_t& nTime, const int64_t& nValue, uint64_t& nWeight);
credit to banzaiBTC as this was his solution for the same error on 1337 |
|
|
|
Not that I know of, it was staking great when I was on 2 mil a couple of weeks ago and now nothing for 3 days
Edit
I've just checked and I've got a lot of generated but not accepted coins, why could that be?
use coin control and check the size of your inputs, larger inputs stake faster. honestly i'm not sure. I take it you've updated your wallet? any network problems? |
|
|
|
I see three kinds of mining: CPU mining by many, GPU mining by some, and DICE mining by the gamblers. hehe.
everyone has at least one gpu like everyone has one cpu, so i think gpu are fair in comparison with cpu, nothing so major in difference asic are the plague not gpu the problem with gpu is farms, yes everyone has at least one gpu but miners generally have a lot more the worries are a bit unfounded imo as i doubt this is profitable for a gpu farm to mine |
|
|
|
Has anybody else having a problem with staking lately? I have just under 3 mil coins and its staking but I haven't received anything for 3 days. Before it was giving me rewards every couple of hours.
i guess anybody with under 3mil may have "problems", total supply is near 1.4bil now. check weight indicator, if it shows expected time above 4-5 hours - that's the problem, low weight im staking ok with 1,690,638 only 3 blocks a day average though @dkmc are your coins split into small inputs by any chance? |
|
|
|
what is going on with this coin?
I was just thinkig of buying some
Is it legit?
abandoned by the look of it |
|
|
|
cant access thealtcoinboard.com any more  error 403 - this web app is stopped |
|
|
|
Will it be necessary to update the wallet straight away or can this be done weeks / (plenty of) months later? Or could this create difficulties?
usually as long as you've updated before the fork you should be fine so the sooner the better (ie as soon as the wallets released) the forks in the 2nd week of may if memory serves |
|
|
|
Fairly distributed POS coin. That is the easiest way to go!
I totally agree with you no expensive mining stuff to buy I think faucets is a good way to distribute this coin but the most important things is the roadmap of this project what is this for and what are the target industry .. there was a coin a while back, faucet I think. It had a unusual distribution method where it distributed coins say 1000 per block or whatever split among active connections (running wallets) once distribution was complete it became pure pos great idea for distributing without mining hardware. my preferred method would be cpu only pow followed by pure pos preferably a new algo or the one espers is using. I'd avoid cryptonote style coins as they're a ball ache to use unless you're computer literate. Things may have changed since I last dipped my toe into them but that's my 2 cents worth. here you go the logo  Love it  |
|
|
|
sure. and i believe that 50sat is very well reachable.
(and now somebody comment how worthless this is)
Now imagine if 300 people from the giveaway are all driving Chevy Tahoes ... ... or Ford Expeditions ... Or just big giant pick up trucks. wooooo! (Personally, I'm buying a barbel for my home gym.) I doubt more than 5 or 6 People from the giveaway would hold that long. Prolly quite a few have already sold some.. still got mine probably hold for a while doubt it'll hit 50 sats but it sure would be nice |
|
|
|
NEW FEATUREI have set up an official MOJOcoin blog Mojocoin Official BlogThis will be the first place we will publish any official updates, alerts, competitions and wallet releases and other important news. The blog is not a discussion forum and only serves as an official channel for updates. It has been set at Medium.com as it is easy to use and clear and I am redirecting the subdomain blog.mojocoin.org there now. I will put together an update re. the hard fork shortly and then update with the wallet links as soon as the wallets have been tested properly. Awesome!! The blog is a great idea, very professional. I agree. I hope this blog will release updates to new wallet soon. it is indeed a great thing to have @PPan there's a post on the Blog regarding the new wallet with a good diagram of a hardfork at the top for those unsure |
|
|
|
Yobit 1337 wallet is now online, off maintenance, open and ready for business. Let's get this pump on. Baby.  probably worth doing a test transaction first ... because Yobit |
|
|
|
@Everyone
Please note that it has been brought to our attention that if you send too small of amount then there will be an issue with the wallet and may cause you to lose coins.
As a temporary fix please insert;
paytxfee=0.01
to your Espers.conf file
This will charge you .01 ESP and thus make it impossible to send an amount lower then that. this will fix the issue. However we will fix this and have the updated client As Soon As Possible.
Thank you for your time,
-Jacob
EDIT; THIS IS ONLY AN ISSUE IF YOU SEND LESS THEN .001 ESP. MOST IF NOT ALL BLOCKCHAINS RUN INTO THIS ERROR JUST DON'T REALIZE IT BECAUSE EVERYONE ELSE CHARGES FEES.
WE DO NOT WANT TO CHARGE FEES EVER. WE WILL FIX THE ISSUE SO YOU WILL STILL NOT BE FEE'D.
I think at one moment - Unique Auto-Generating Configuer
rewrote my custom written (which had only addnodes in it) espers.conf with auto generated one. So it might happen -iThink- that paytxfee=0.01 would not be in new auto generated one.. with wallet restart?... or it creates it only once till erased? but coins can be saved with private key. so it doesnt matter beaten to it by cryptocoderz but No I've been using a custom conf file since day one |
|
|
|
...
I'll list my connections when I get home if it's useful to you
That'd be great. I only see the one mentioned above too. here ya go mate: 18:15:40

getpeerinfo
18:15:40

[
{
"addr" : "192.95.29.72:33961",
"services" : "00000001",
"lastsend" : 1461604477,
"lastrecv" : 1461604476,
"conntime" : 1461526496,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 353890,
"banscore" : 0
},
{
"addr" : "176.37.23.74:58925",
"services" : "00000001",
"lastsend" : 1461604476,
"lastrecv" : 1461604476,
"conntime" : 1461526502,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 353883,
"banscore" : 0
},
{
"addr" : "5.9.36.211:35376",
"services" : "00000001",
"lastsend" : 1461604476,
"lastrecv" : 1461604476,
"conntime" : 1461526505,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 353882,
"banscore" : 0
},
{
"addr" : "176.37.23.74:30890",
"services" : "00000001",
"lastsend" : 1461604476,
"lastrecv" : 1461604476,
"conntime" : 1461556802,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 354813,
"banscore" : 0
},
{
"addr" : "89.204.153.193:58506",
"services" : "00000001",
"lastsend" : 1461604477,
"lastrecv" : 1461604476,
"conntime" : 1461577592,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 355257,
"banscore" : 0
},
{
"addr" : "176.195.61.91:50342",
"services" : "00000001",
"lastsend" : 1461604476,
"lastrecv" : 1461604476,
"conntime" : 1461587446,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 355378,
"banscore" : 0
},
{
"addr" : "109.172.53.97:49894",
"services" : "00000001",
"lastsend" : 1461604477,
"lastrecv" : 1461604476,
"conntime" : 1461595289,
"version" : 60014,
"subver" : "/Satoshi:2.0.0/",
"inbound" : true,
"startingheight" : 350707,
"banscore" : 0
}
]
|
|
|
|
Hi, We've added XLTCG to the miners multipool: www.zpool.caCheers! Great News, Thank You  Thanks, can someone post some more nodes? Seems to only pickup one.... Anyone... 86.5.28.9:48521 - the one active node I see at the moment, if this helps Seems like we need a rebrand... I'll list my connections when I get home if it's useful to you |
|
|
|
but how do they taste? |
|
|
|
problem building new wallet on linux -Ibuild -o build/coincontroldialog.o src/qt/coincontroldialog.cpp
src/qt/coincontroldialog.cpp: In member function ‘void CoinControlDialog::updateView()’:
src/qt/coincontroldialog.cpp:637:102: error: no matching function for call to ‘WalletModel::getStakeWeightFromValue(int64_t, const int64_t&, uint64_t&)’
model->getStakeWeightFromValue(out.tx->GetTxTime(), out.tx->vout[out.i].nValue, nTxWeight);
^
src/qt/coincontroldialog.cpp:637:102: note: candidate is:
In file included from src/qt/coincontroldialog.cpp:6:0:
src/qt/walletmodel.h:100:10: note: void WalletModel::getStakeWeightFromValue(const qint64&, const qint64&, quint64&)
void getStakeWeightFromValue(const qint64& nTime, const qint64& nValue, quint64& nWeight);
^
src/qt/walletmodel.h:100:10: note: no known conversion for argument 3 from ‘uint64_t {aka long unsigned int}’ to ‘quint64& {aka long long unsigned int&}’
make: *** [build/coincontroldialog.o] Error 1
|
|
|
|
i've read about, por, what is por?
It is called Proof of Reliability no other coin has this feature as it was invented by the Espers team yes but what is it? how it work? earlier in the thread ...
Well we will have a better explanation for PoR once we release the whitepaper however to give you an idea it will be like PoS in the sense that all you need to do is leave your wallet online and connected. Depending on the number of connections you have will determine how many coins (as a base number) you will receive per block for supporting the network and keeping your client online.
To prevent network abuse or users running 100 virtualized or local machines to attempt to generate a massive about per block the nodes will be used as controlling connections (or limiters) as to keep connecting clients inline. In a sense if you have 1200 connections and the nodes which connect to ALL client only see 500, because you are trying to generate more coins than a client should be, the nodes will reject the client's ability to receive a payout do to network abuse (in an effort to keep the system from being exploited).
Additionally the ballance you hold will act a multiplier against the base amount you would receive from the number of connections you have.
In otherwords this is a system that pays you for supporting the network without the biased of bagholders and whales to affect the system.
|
|
|
|
Quick update re. the wallets. We are now testing the final version and just started testing the staking now, should be a day or so to complete, you can see we are running the new wallet on the block explorer:
[img]
Here is a screenshot of the new wallet we are testing. I know it's with the old logo still. It might look a little bit different when we're done.
[img]
Almost there...
nice looking wallet, I look forward to the release |
|
|
|
...
We will work on it.
you guys respond quickly, nice. looking forward to seeing where this goes  |
|
|
|
|
Show Posts
a good example of feedback being useful 
