Thanks, sir! I am using the legacy wallet now, but will try it in another computer
Just in case I've created a misunderstanding - by "MOVING the wallet aside", I meant moving the file wallet.dat to somewhere safe. The approach should work irrespective of which CLAMS client you are running. Cheers Graham |
|
|
|
Cryptocurrency is a brutal, predatory space where unprotected and unsecured networks are destroyed for the slightest bit of value.
If you think any coin that survived four years is a sh1tcoin, think again.
Interesting. Whilst that may be an apparently plausible/popular opinion, it's a long way from the ( far more prosaic) reality. Cheers Graham True that.  Apologies for my poor formatting, I edited my original post to make the comment credit more clear. Cheers Graham |
|
|
|
Interesting. Whilst that may be an apparently plausible/popular opinion, it's a long way from the ( far more prosaic) reality. Cheers Graham Edit: clarified origin |
|
|
|
I think i found a problem with the pre-release version of clam. A issue has been opened in github, but i replicate here so maybe someone can help me:
One thing to try. If you have a funded wallet, try MOVING it to one side and using a fresh empty wallet until the client is fully synced (you probably need to start from 0 again, a bootstrap.dat is useful) and then stop the client and switch back to the funded wallet before restarting. Sometimes a client will attempt to stake before it is fully synced, causing a local (and unfortunately, permanent) hard fork. Cheers Graham |
|
|
|
A question about the PoS and its effect on the wallet stability.
Is there a way to improve this, the possibility of using just a small amount of the balance to be able to stake without affecting the wallet response is not really great.
The problem description is rather vague, you are far more likely to get coherent and relevant responses if you can be more specific in describing the problem. Cheers Graham |
|
|
|
It means, that SLM on Nova are lost, if they cant fix the problem???
Sorry, I can't speak for Novaexchange so please don't ask. As I mentioned, they're experiencing a problem with change addresses not behaving in the way they need. Lost change wasn't a problem before but they're under new ownership and it is now, to the extent that they are prepared to delist rather than tolerate the problem. I can't really conceive how you equate that with "lost". Cheers Graham |
|
|
|
I wonder what the problem could be, as the SLM wallet was working fine on Novaexchange before they closed down last year.
Issue was broached on Discord. Apparently they are experiencing problems with change addresses, previously the problem was seen as ignorable but that's no longer the case. They're basically asking for the wallet to be reprogammed to suit the exchange back-end or basically be delisted, their stance is that the wallet behaviour is incorrect. Same goes for Peercoin. I didn't understand the description of the problem and responded to that effect. They indicated that they'd try and formulate the issue more clearly. That was a week or so ago. Cheers Graham |
|
|
|
I have around 7% difference between my wallet and the bchain explorer.
I have also one empty wallet (no burning) that still contains few thousands of coins on the bchain explorer.
Because the problem cannot be replicated, it's near-impossible to provide constructive help. Anyone else experiencing this issue? Anyone have any practicable ideas on how to reproduce the problem? Cheers Graham |
|
|
|
I just wanted to access ACME ( http://tessier.bel-epa.com:5064) to know if I could find keliokan's problem, but it didn't work, is it currently offline? (minkiz.co works again). It's elderly kit, overdue for upgrade. The server was getting overwhelmed. I decided to allocate some more RAM to Fuseki , seems to have eased things somewhat. I have a browser tab open on Hetzer's server auction page, I'm that close to reprovisioning  Cheers Graham |
|
|
|
Good day, devs!
The idea will be fortunate!
Sober results, impeccable website, engaging design!
Oh dear, little better than a Markov chain. And clickbait headlines are saying that GAI is imminent (which I'll read as: "no more imminent than it was 30 years ago"). Honestly, just semi-random shuffling of a text corpus will get you quite a long way, as I trivially demonstrate in Minki's "Hodlerscope": https://minkiz.co/hodlerscopeCheers Graham |
|
|
|
Hi, Mr. Higgins
I'm not as old-school as my writing style might lead one to believe Happy to be addressed as "Graham" but also perfectly happy to acknowlege societal differences. I got around that little error by ./configure --without-miniupnpc
Makes sense for a coin daemon on the open subnet but many Linux users are safely NATted away on a local network and I've found that modern routers handle UPNPC quite nicely (although my asynch internet connection suffers a bit from the incoming calls taking up bandwidth but that's the penalty for running a full node on a local network, aiui). It'll depend on your Linux distro and its C++ version, for my Mint 18.X distro, the correct syntax is, apparently:
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,66);
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5);
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,194);
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E}; // xpub
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4}; // xprv
But, YMMV depending on your distro and version of C++. For altcoin archeology/forensics, I've started to use VMs of LInux distros contemporary to the launch date of the coin. I am currently downloading the blockchain with a auto-generated wallet.dat file however, so I got it "working" on Debian.
Will keep testing it......
Just to satisfy my curiosity, which Debian version? Cheers Graham |
|
|
|
I was trying to build for the first time using Debian.
The Gapcoin codebase remains unchanged from its Jan 2015 state ( https://github.com/gapcoin/gapcoin/commits/v0.9.2-gap). Whilst the (then-contemporary) OS X and Windows binaries continue to function on today's modern distros, that isn't true of the Linux world, you will run into errors if you try to build using a modern Linux distro because, as you have discovered, some Linux libraries often introduce backwards-incompatibility. I was not aware of the PoWUtils.h error until now but you have it backwards I figured it out, but not sure as the real problem I was having was Debian updated OpenSSL to 1.1.0-dev after I switched to 1.0.2-dev. That fixed most of it.
fwiw, I wouldn't expect to be able to build a Linux codebase that's been unmaintained for years without first addressing the backwards-incompatibilities, especially if the dependencies include boost, Qt and openssl. But I thought it would build up until this error it fails on Debian. Hope you can figure it out.
devlist = upnpDiscover(2000, multicastif, minissdpdpath, 0, 0, &error);
The miniupnpc library is repeatedly not backwards-compatible, see https://github.com/slimcoin-project/Slimcoin/blob/master/src/net.cpp#L873 for the version switches I added to Slimcoin, it should be just a copynpasta solution. In other circumstances, I'd create a helpful Pull Request but in this instance it'd be a waste of my effort/time as it seems fairly clear that the dev has made a deliberate choice not to actively maintain the Gapcoin github repos. HTH, Cheers Graham |
|
|
|
Why some wallets cannot be found on the explorer ?
Too little info and therefore confusing. Which explorer and which wallets? Cheers Graham |
|
|
|
Considering Gapcoin fails to build on every single operating system except Trisquel I would assume the value is appropriate. I don't mind but even Trisquel will upgrade past Boost 1.58 and OpenSSL 1.0.2.
There is not a single distribution with updated software in which Gapcoin will build now. You can update outdated OpenSSL using a different repository until OpenSSL no longer maintains 1.0.2, but it is extremely difficult to downgrade Boost 1.62 to Boost 1.58 to get it to build.
I seem to be inordinately lucky then because (coincidentally) just last night I successfully compiled the git repos checkout on Mint 18.2 (after correcting for the known problems in rpcrawtransaction.cpp and PoWUils.h). Changes to the Linux distro packages means I need to add CPPFLAGS=-fPIC CXXFLAGS=-fPIC to the make command but other than that, it seemed to be a standard autotools build. Am I missing something? Cheers Graham
PoWCore/src/PoWUtils.h:299:5: warning: identifier ‘constexpr’ is a keyword in C++11 [-Wc++0x-compat]
static constexpr double accuracy = 7.105427357601002e-15;
^
--- a/src/PoWUtils.h
+++ b/src/PoWUtils.h
@@ -296,6 +296,7 @@ class PoWUtils {
static const uint64_t log_150_48 = 0x502b8fea053a6LL;
/* 1.0 / 2^47 (for debugging) (not 48 bytes because rounding errors could count as failure) */
- static constexpr double accuracy = 7.105427357601002e-15;
+ static const double accuracy = 7.105427357601002e-15;
/**
rpcrawtransaction.cpp:299: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>’
--- a/src/rpcrawtransaction.cpp
+++ b/src/rpcrawtransaction.cpp
@@ -296,7 +296,7 @@ Value listunspent(const Array& params, bool fHelp)
CTxDestination address;
if (ExtractDestination(pk, address))
{
- const CScriptID& hash = boost::get<const CScriptID&>(address);
+ const CScriptID& hash = boost::get<CScriptID>(address);
CScript redeemScript;
if (pwalletMain->GetCScript(hash, redeemScript))
entry.push_back(Pair("redeemScript", HexStr(redeemScript.begin(), redeemScript.end())));
|
|
|
|
now i have another problem
I cannot transfert my coins on another wallet...
all transaction above 500 are rejected...
You have a case of "UTXO bloat", i.e. have accumulated a large number of small staking tx. When you send 500 SLM, the total is composed of many of these small stake reward txs and that can easily exceed the max number of inputs per tx. Consolidate your small change into larger amounts by sending to yourself - as you are doing - but start small (a few 10 SLM tx) and work your way up. Cheers Graham |
|
|
|
This (obviously canned) patronising and sadly ill-infomed response on their website marks them down as safely ignorable: The policy with the dead coin list is, it is hard to get on and hard to get off. Coins and tokens only get added if we think they have a almost 100% chance of failure. As of right now Coinmarketcap has listed this coin inactive. You guys need to get on some exchanges and get some momentum.
Also getting off the list is possible and being on it is not a bad thing if you are just listed for Low Volume like lots of the coins are.
Also lots of the time Scam devs pick up projects listed on coinmarketcap because it is a great place to start. Due to exposure, link juice, referral links.
1) Find a low ranking coin listed on coinmarketcap
2) Buy up large
3) pump the price up with a few updates and some social
4) Sell off
It will not be long before Coinmarketcap and other similar places require a minimum volume to be listed.
Starting a currency is a big responsibility, similar to putting a stock on a exchange. and our dead coin cirtera is fair and unbiased, we have no connection with any of these coins.
Will update the age started.
Cheers
PS if your coin gets in the top 500, we will do a review for it. 🙂
Cheers Graham |
|
|
|
What does Gapcoin's PoW do that Bitcoin's PoW doesn't do?
... Functional Mathematical Optimization (of Prime Number Gaps) on a Blockchain? ...
I'll bite: Uses Functional Mathematical Optimization of Prime Number Gaps to secure the Public Ledger. Cheers Graham |
|
|
|
The problem still exists though
If you personally don't have/have access to the skills/knowedge to resolve an apparent problem with the code, then the widely-accepted approach in open source software - and here, too - is to carefully describe how to reproduce the problem and raise a github issue. It would be a good idea to post a reference here after doing so. If you read up-thread, you will encounter BayAreaCoins' periodic mentions that an upgraded version of the code is being developed ( https://bitcointalk.org/index.php?topic=623147.msg34414705#msg34414705), earlier posts advise that development takes place sporadically, as and when donation funding is available. Also, if you do read up-thread, you will encounter more of dooglus' posts and that might give you an opportunity to reflect on what your insinuations have communicated publicly of yourself. You've got more money than I have time so I'll leave you to it. Cheers Graham |
|
|
|
No we can't agree.
Then we're done. Cheers Graham |
|
|
|
What are you on about mate, demands?
Posting that you've PM'd dooglus and are awaiting a response. Can we agree that this is putting public pressure on someone that you have assumed will take personal responsibility for fixing a problem? Cheers Graham |
|
|
|
|
Show Posts
