Can't connect. Any working nodes?  107.170.219.99:53826
128.204.24.52:60001
178.44.105.129:1421
178.90.195.228:19646
212.98.191.170:64584
31.181.247.251:55793
5.9.56.229:33463
69.253.31.197:56409
69.253.31.197:61251
83.136.243.162:58155
85.10.194.50:8373
94.241.218.78:59770
Cheers Graham |
|
|
|
Hi Thomas, The status is that the currency is working, and usable for the intended purpose, but there just doesn't seem to be enough interest in this to justify taking it on to mainnet in a full release.
To be brutal, it's unfinished and advertises itself as such. A lack of polish and inadequate documentation exacerbate the unfinished feel and together, all three form the primary cause of the low level of interest expressed. The latter issues can be remedied relatively easily, leaving “just” the resolution of the described implementation issues to be addressed, either in code or in documentation. Unit tests and coverage reports would go some way towards countering the project's current overall ambience of “mad scientist code dump”. Cheers Graham |
|
|
|
Someone posted a graph of new coin launches over time.
 <-this one? If so, it's updated regularly and currently available on Minkiz' landing page: https://minkiz.coThe chart is a rendering of the publicly-[available|owned] DOACC altcoin metadata collection ( https://github.com/DOACC/individuals). I have a holiday task of writing the documentation that describes the principles and coverage of DOACC, plus how the data can be used very simply to create charts like the above.Cheers Graham |
|
|
|
looks like ziftrCOINs has just cloned spread algorithm and changed X11 for keccak. By the date, i'd say it's quite possible! Is their code available? BTW, Keccak is not memory hard. Those guys got something wrong!
Imitation is the sincerest form of flattery but it's not a reassuring signal that they chose to be coy about the origin. The code isn't available AFAICT, so my default is to consider it to be proprietary and closed-source. The unforced error of describing Keccak as “memory hard” doesn't fit very well with the size of the team implied by https://www.ziftrcoin.com/about-us/ziftr-team, are they all clueless? But at least they seem to be a properly registered US commercial entity (as myVBO): http://investing.businessweek.com/research/stocks/private/snapshot.asp?privcapId=105672715“myVBO LLC offers a Web based centralized information management software solution for small businesses. Its solution gathers business data, information, news, and business tools together in a Web portal; provides accounting, payroll, online meetings, and email marketing services; and enables customers to search Internet and rate Web sites. The company also offers real-time business statistics via QuickBooks and Google Analytics, stock tracking, news and video feeds, and market and price history on products, as well as enables customers to purchase products via the MyVBO purchasing engine. In addition, it offers a professional networking area for business professionals to discuss issues of th...”
I'm currently entertaining myself by imagining the consequences if Mr Spread's anti-pool solution was ported to Bitcoin <giggle>. Cheers Graham |
|
|
|
Interesting concept -- I've browsed through most of the thread but haven't seen a clear answer on a key point:
How specifically are mining pools avoided with this coin?
I must admit, I'm a bit hazy on the detail too. Maybe SPR could do with a one-para summary and a snappy buzzphrase? Something along the lines of the “Sign-to-Mine™” approach taken by by Ziftrcoin and described thusly: “We will use the NIST chosen Keccak, a memory-hard 512-bit hashing algorithm, along with our Sign to Mine™ protocol, to mine ziftrCOINs. Essentially, the header must contain a signature of the header’s contents, which must be verified with the script spending the coinbase transaction. This ensures that the one who solves the block also has the capability to spend the block, which limits large pools. With Sign to Mine, miners should make sure they trust those with whom they are mining, as anyone in the pool has the ability to spend the reward for the blocks they solve.” Quoted from ”ziftrCOIN Specifications, Released December 6, 2014” https://d19y4lldx7po3t.cloudfront.net/assets/docs/ziftrcoin-coinspecs.pdfThey may even have actually registered the trademark. Cheers Graham |
|
|
|
eventually when i have time i may add it to abe
Okay, I can do that --- but for a PR to make any sense, sifcoin-hash needs to be available to install from PyPi (which it now is). TBH, I really doubt whether the PR will ever get merged because it proposes to add a Chain subclass with a known unmanaged dependency (i.e. sifcoin-hash) for which the requirement kicks at runtime and it's a showstopper for what would be reasonably expected to be a supported configuration. I think this is why most algo-specific Abe variants inhabit their own fork, it allows the maintainer to include the specific supported hash function as a subdir, thus enabling the dependency to be advertised and imposed at install time. Whatever, the edited bitcoin-abe fork is https://github.com/gjhiggins/bitcoin-abe, PR is https://github.com/bitcoin-abe/bitcoin-abe/pull/155The supporting sifcoin-hash module is https://github.com/gjhiggins/sifcoin-hash and on PyPi: https://pypi.python.org/pypi/sifcoin-hash/1.0.2you and I appear to be the only two people doing any development (even part time) work on this coin....
Sifcoin's innovation of using a folklore hash combiner makes it one of the more notable members of the altcoin technical engineering heritage. Cheers Graham |
|
|
|
Thing is, a year ago we had several hundred less altcoins.
I guess we're near enough to the end of the (calendar) year for gubmint work ... This SPARQL query, when posed of the DOACC metadata (RDF graph), will return a count of coins with an incept (YYYY-MM) date in 2014: PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT (COUNT(?node) as ?ncoins) {
?node doacc:incept ?incept .
FILTER(?incept > '2013-12'^^<http://www.w3.org/2001/XMLSchema#string>) .
FILTER(?incept < '2015-01'^^<http://www.w3.org/2001/XMLSchema#string>)
}
atm, it yields a total of 1627 <- altcoins launched (or at least lofted) in 2014 (thus far, give or take a handful). For extra credit, elaborate the query a little: PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT DISTINCT ?incept (COUNT(?node) as ?ncoins) {
?node doacc:incept ?incept .
FILTER(?incept > '2013-12'^^<http://www.w3.org/2001/XMLSchema#string>) .
FILTER(?incept < '2015-01'^^<http://www.w3.org/2001/XMLSchema#string>)
} GROUP BY ?incept ORDER BY ?incept
pass it over to sgvizler to handle the posting of the query and the rendering of the results as a chart: Looks like 2014 was the Year of the Altcoin. Obviously not all will survive, some have already failed. Maybe the title should have read “All altcoins will survive. Discuss.” You can run the “2014 total coins” query for yourself by pasting it into the textarea on https://minkiz.co/sparql or following this pre-completed link.Cheers Graham Edit: added DOACC url |
|
|
|
a git pull to add support to official abe on github
...
jtobey regularly adds different algorithms....
Regrettably ... I no longer work with Abe
Cheers Graham |
|
|
|
p.s. I apologize to the Ridiculous community, if such a coin exists.  It's a reasonable bet that you're safe on that one; here's a full list of every coin name / symbol that we could find a trace of: https://minkiz.co/coin/name/Cheers Graham |
|
|
|
From a branding perspective, it promises to be way more trouble that it's demonstrably worth.
Ach, never mind. I'd failed to spot the design document's note: “This document describes inventions by NewGamePlus Inc. that are patent-pending with the USPTO.”Cheers Graham |
|
|
|
As a pun, it's rather twee and I predict that you will regret deeply the expense of the indulgence.
For marketable high-level concepts I believe it's more important to focus on branding to differentiate our ideas from those of our competitors. The puns are of course part of the branding -- Qoinapps (Blockchain Applications), Qointracts (Smart Contracts), Transaqoins (Smart Transactions?), Entangled Chains (Multi-Chains). These are things users and developers will be using on a daily basis, so a developer can search for say "qointracts" instead of "smart contracts" and find a relevant answer pertaining to Qointum. We have more sensible names for technical concepts -- Maximally Vetted Delegate Chain, etc. Thanks for responding, I'm keen to see how you get on with developing a brand identity, values, story, etc. My main objection is that you're replacing reasonably straightforwardly recognisable labels with labels that must first be decoded as puns. This adds to the mental load rather than reducing it. Just for clarity, I'm not questioning the approach (of attending to branding) but the implementation. Unless you've got support from either desk research or quantitative work, then you're merely guessing at the effectiveness of the linguistic differentiation that you're proposing will somehow play into your branding. How will it translate across languages? (Hint: not at all). Also, (largely because I think you've actually got something substantial and could with real support to keep you on the straight and narrow), I'm going to call your bluff on “... using on a daily basis, so a developer can search ...” I reckon that's just a guess on your part because you have no evidence for its pertinence to this context. Sounds as if there's little to no current MR support to drive this aspect of the development of a brand identity. You're not the first person to have had the notion; all previous attempts to rope in punning linguistic markers to promote brand identity have basically sunk without trace because the proponents ignored the fact that what's humorously quirky to one is pretty much guaranteed to be irritatingly unfunny to another. It's not as effective a tactic as you seem to believe and its inability to cross alphabets is likely to prove a major disadvantage in a global market. It also has the penalty that if the project is in any way successful, the IP in the brand naming will need to be protected proactively --- which means enforcing “Qointract™” (or whatever) in every usage. From a branding perspective, it promises to be way more trouble that it's demonstrably worth. Cheers Graham |
|
|
|
Qointracts
Yeah it was too tempting of a pun. As a pun, it's rather twee and I predict that you will regret deeply the expense of the indulgence. Successfully expressing complex concepts clearly and concisely is difficult enough as it is without gratuitous distractions, however humorously intended. Cheers Graham |
|
|
|
difficulty still up and down but never dropping too low,
At one point, I hacked up a Python sifcoin-hash module ( https://github.com/gjhiggins/sifcoin-hash) to get a Sifcoin version of Abe up and running: datadir = [
{
"dirname": "/home/gjh/.sifcoin",
"chain": "SiFcoin",
"policy": "SiFChain",
"code3": "SIC",
"address_version": "\u0010",
"script_addr_vers": "\u0005",
"magic": "\u00f2\u00d5\u00d3\u00d8",
"loader": "blkfile", # See the comments for default-loader below.
"conf": "sifcoin.conf"
}
]
The Abe.Chain.SiFChain subclass is quite straightforward ... # Copyright(C) 2014 by Abe developers.
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Affero General Public License as
# published by the Free Software Foundation, either version 3 of the
# License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Affero General Public License for more details.
#
# You should have received a copy of the GNU Affero General Public
# License along with this program. If not, see
# <http://www.gnu.org/licenses/agpl.html>.
from . import BaseChain
class SiFChain(BaseChain):
"""
A blockchain that hashes block headers using the SiF algorithm.
The current implementation requires the sifcoin_hash module.
"""
def block_header_hash(chain, header):
import sifcoin_hash
return sifcoin_hash.getPoWHash(header)
Also, fwiw: on a whim, I transcribed the Sifcoin code back into the full commit history, added getnetworkhashps to the API and squeezed a “diffplot” chart on to the overview page: https://github.com/gjhiggins/sifcoin/commits/diffplotCheers Graham |
|
|
|
I missed this coin in the early time  Easy to miss, the coin was quite low profile early on (launched 29 July 2014) and wide-scale interest is only just kicking in. You may find it worth skimming through the old posts on this thread to get a sense of the high level of cohesion and confidence in the dev that was shown by the early community, e.g. the way this: https://bitcointalk.org/index.php?topic=715435.msg8553565#msg8553565 played out. Cheers Graham P.S. Mr Spread, 3 PRs for your consideration. |
|
|
|
One of the arguments I have heard against Dogecoin is that it does not have proper developers.
I can't see why you'd lend that statement any credence whatsoever, it's merely an instance of the “no true Scotsman” fallacy. The criterion term “proper developers” is left undefined, rendering the claim vacuous. By the same token, one could equally claim that no cryptocurrency has proper developers or that no cryptocurrency could ever have proper developers. Cheers Graham |
|
|
|
any nodes???
getpeerinfo
[
{
"addr" : "128.72.130.145:20703",
"services" : "00000001",
"lastsend" : 1417695144,
"lastrecv" : 1417695143,
"conntime" : 1417695142,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 283401,
"banscore" : 0
},
{
"addr" : "192.99.37.224:20703",
"services" : "00000001",
"lastsend" : 1417695896,
"lastrecv" : 1417695896,
"conntime" : 1417695143,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 283401,
"banscore" : 0
},
{
"addr" : "37.26.137.217:20703",
"services" : "00000001",
"lastsend" : 1417695880,
"lastrecv" : 1417695881,
"conntime" : 1417695143,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 283401,
"banscore" : 0
},
{
"addr" : "219.210.132.3:20703",
"services" : "00000001",
"lastsend" : 1417695881,
"lastrecv" : 1417695881,
"conntime" : 1417695150,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 283401,
"banscore" : 0
},
{
"addr" : "137.135.60.66:1176",
"services" : "00000001",
"lastsend" : 1417695593,
"lastrecv" : 1417695321,
"conntime" : 1417695216,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 283374,
"banscore" : 0
},
{
"addr" : "176.104.69.157:55316",
"services" : "00000001",
"lastsend" : 1417695675,
"lastrecv" : 1417695321,
"conntime" : 1417695271,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 283392,
"banscore" : 0
}
]
Cheers Graham Edit: updated peer data with currently-synced addresses |
|
|
|
Is this coin dead?
Using a Red Book analogy, it's currently “critically endangered”: "addr" : "94.199.74.202:1217",
"addr" : "91.156.103.152:1217",
"addr" : "198.23.161.59:52508",
getmininginfo
{
"blocks" : 32402,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00669779,
"errors" : "",
"generate" : true,
"genproclimit" : 1,
"hashespersec" : 60242,
"networkhashps" : 61368,
"pooledtx" : 0,
"testnet" : false
}
Cheers Graham |
|
|
|
the distinction is between Nectar and NectarCoin ... We've tried to cover all of the bases here.
You missed one - the ANN title: [ANN][SWEET] Nectar | Crypto's "P2P Skype" | All-in-One "Sweet Suite" | 5+ PODThanks for clarifying the distinction, I've ensured that it appears correctly as “Nectarcoin” in the DOACC metadata collection. Cheers Graham |
|
|
|
|
Show Posts
