I'd re-check that, if I were you. Cheers Graham |
|
|
|
HTH
It might do, if accompanied by the next step --- which is basically: “gimme me all ya got on D72f28a0f-7726-4710-a249-f126027c402e” (assuming you're keen to learn more of Rivr) ... PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?p ?o WHERE { doacc:D72f28a0f-7726-4710-a249-f126027c402e ?p ?o }
and if you wanted the simplest format, without any user-friendly PREFIX shortcuts: SELECT ?p ?o WHERE { <http://purl.org/net/bel-epa/doacc#D72f28a0f-7726-4710-a249-f126027c402e> ?p ?o }
I'll include the (again, lightly-edited) results but they're not really intended for direct human consumption, the purl.org URLs are best left to a Linked Open Data explorer, it's just the strings that we're interested in and the bcttalk URL ... | http://purl.org/net/bel-epa/doacc#coin | http://purl.org/net/bel-epa/doacc#D4edf512b-0c38-49b1-b71c-a4d34629bffc | | http://purl.org/net/bel-epa/doacc#image | "/img/coins/rivrcoin_rivr.png" | | http://purl.org/net/bel-epa/doacc#incept | "2014-07" | | http://purl.org/net/bel-epa/doacc#pow | http://purl.org/net/bel-epa/doacc#D19155d96-f19d-4976-8f20-6434e3599186 | | http://purl.org/net/bel-epa/doacc#comment | "pending" | | http://purl.org/net/bel-epa/doacc#protection-scheme | http://purl.org/net/bel-epa/doacc#D9758d7c9-6b22-4039-a325-285d680c22fe | | http://purl.org/net/bel-epa/doacc#protocol | http://purl.org/net/bel-epa/doacc#Db8ade99f-11f1-476b-ae77-03c005c1bb66 | | http://purl.org/net/bel-epa/doacc#release | http://purl.org/net/bel-epa/doacc#D54b30ca0-6326-41cd-a142-1897298a9d51 | | http://purl.org/net/bel-epa/doacc#symbol | "RIVR" | | http://www.w3.org/2000/01/rdf-schema#comment | "Rivr is an attempt to redesign the theory of decentralization using the Bitcoin protocol, by being the first digital cryptocurrency that introduces the monitary concept of debt as money in a trustless Peer-2-Peer environment. Rivr aims to involve the further abstraction of cryptocurrency into other exchangeable assets and the accumulation of income through ownership, exchange & interest., Our Proof-of-stake model derives from the Pareto distribution. Similar to the concept of pool mining, we recognize that the majority of results often comes from a minority of inputs, driving the economy forward. Introducing the Rivrbank prescript, users will soon have the ability to exchange, borrow and save stakeweight - against interest!, Make sure you check out our Development Process Report for daily updates, POOLS:, http://www.hashharder.com/x13/rivrcoin, http://rivr.hashhot.com, http://www.flash-mine.com/, http://rivr.minerpools.com, Source: https://github.com/rivr/rivr, Windows: https://mega.co.nz/#!Mo4EjCLL!4M1-zC75SiXQMo4BI84prYfEjcsL6RA2ei3cDtLpFc8, Linux, MAC, Android" | | http://www.w3.org/2004/02/skos/core#prefLabel | "RivrCoin"@en | | http://purl.org/net/bel-epa/doacc#thread | https://bitcointalk.org/index.php?topic=719466.0 | | http://www.w3.org/1999/02/22-rdf-syntax-ns#type | http://purl.org/net/bel-epa/doacc#Cryptocurrency | | http://www.w3.org/1999/02/22-rdf-syntax-ns#type | http://purl.org/net/bel-epa/doacc#Repository | | http://purl.org/net/bel-epa/doacc#date-founded | "2014-07-31" | | http://purl.org/net/bel-epa/doacc#premine | "non" | | http://www.w3.org/2000/01/rdf-schema#label | "RivrCoin" | | http://purl.org/net/bel-epa/doacc#total-coins | "2900000" | | http://purl.org/net/bel-epa/doacc#block-time | "7200" | | http://purl.org/net/bel-epa/doacc#confirmations | "100" | | http://purl.org/net/bel-epa/doacc#distribution-scheme | http://purl.org/net/bel-epa/doacc#Dc10c93fb-f7ec-40cd-a06e-7890686f6ef8 | | http://purl.org/dc/elements/1.1/title | "RivrCoin"@en | | http://purl.org/net/bel-epa/doacc#repository | http://purl.org/net/bel-epa/doacc#D7ad347e6-4059-4e79-8b19-02da2615f95c | | http://purl.org/net/bel-epa/doacc#source | https://github.com/rivr/rivr |
Cheers Graham |
|
|
|
Hi
In order to try a project I'd like to know which altcoins are recent and have a long block creation time (ie small number of blocks per day)
Thanks
Y'know, I'm rather glad you asked that question  The Description Of A CryptoCurrency project (DOACC - https://github.com/DOACC) carries metadata for over 1600 altcoins and publishes it as an RDF graph. Minkiz offers a SPARQL endpoint at http://minkiz.co/sparql. You can use the SPARQL endpoint via the web form at that URL, it is pre-completed with an example query. If you over-paste the following query into the box .... PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?node ?label ?symbol ?incept ?bt WHERE {
?node skos:prefLabel ?label .
?node doacc:incept ?incept .
?node doacc:symbol ?symbol .
?node doacc:block-time ?bt .
FILTER (?incept > "2013-12" && ?bt > 300)
} order by ?bt
it will return a list of altcoins which satisfy the query statements, giving the coin's DOACC uuid4 unique reference, the name of the altcoin, its trading symbol, the month of its inception (all entries have at least a YYYY-MM incept date, some have a full YYYY-MM-DD date-founded) and the block target time in seconds. Feel free to tweak the target values (atm, incept date later than "2013-12" and block target time greater than 300 seconds). and for the terminally curious, the results (lightly edited in the interests of brevity and clarity) ...
------------------------------------------------------------------------------------------
| node | label | symbol | incept | bt |
==========================================================================================
| doacc:Dbe503204-7558-4362-94fb-d0fde4998b3a | Bulbcoin | BULB | 2014-08 | 380 |
| doacc:D0d94412d-27fd-4326-957e-a192e34254c0 | DiamondBack | DBK | 2014-08 | 384 |
| doacc:D9d7c7700-a2cb-40c4-aa52-859ad80bbf8e | 419coin | SCAM | 2014-04 | 419 |
| doacc:D52624384-c024-4497-b44f-e0a803c5923d | Pxlcoin | PXL | 2014-01 | 420 |
| doacc:Dee298eff-b026-4480-9a89-f70255f096c4 | Auroracoin | AUR | 2014-02 | 600 |
| doacc:D5a5921bb-6700-4a56-9bf6-558af5b2f7f7 | Arkhash | ARK | 2014-03 | 600 |
| doacc:D79ffc442-dddc-41da-822c-2f7fb4017f40 | BitcoinNEW | BTN | 2014-04 | 600 |
| doacc:D4f9acba8-77b5-4875-add3-4fe3da74c313 | Lemonadecoin | LEO | 2014-05 | 600 |
| doacc:Da47a45e7-540a-44cd-90df-b9c09d07c479 | Metalcoin | MTC | 2014-06 | 600 |
| doacc:Df73a7291-147f-4b6d-b04d-9a6e190b2e2c | Zippercoin | ZIP | 2014-06 | 600 |
| doacc:D0e92be0b-24a7-405c-9d7d-838e8de54a10 | BigBullioncoin | BIG | 2014-07 | 600 |
| doacc:Def44a8b7-1825-490c-a271-f4929ba94b9c | CherryNote | CRR | 2014-07 | 600 |
| doacc:D4c23219d-ead1-4a97-bea1-b1339ae8faaf | Eaglecoin | egc | 2014-07 | 600 |
| doacc:Da0770ce7-0c77-4295-b225-a54a277a7828 | SpreadCoin | SPREAD | 2014-07 | 600 |
| doacc:D61d7490f-b92a-4475-ba84-4fe5e929117d | ASDcoin | ASD | 2014-08 | 600 |
| doacc:D944be229-25c2-4569-971c-5ca8999ecf68 | Nostrum | NOS | 2014-09 | 600 |
| doacc:D88c5d412-9baa-4907-8408-c6c953ec122a | Asspenny | ASS | 2014-04 | 720 |
| doacc:Dfd347290-f43c-4172-94f6-8b31aa207fc4 | Spirecoin | SPIRE | 2014-02 | 900 |
| doacc:D4cd50334-925a-425e-8a63-e294c04e1f84 | Arkenstone | ARS | 2014-05 | 900 |
| doacc:Dbd5c4ce0-9e46-463b-b014-6181b605292c | Irccoin | IRC | 2014-04 | 1200 |
| doacc:D9cc029d2-3c3f-4741-a4fd-6928e5253a09 | EdisonX3 | EDISON | 2014-03 | 1800 |
| doacc:D72f28a0f-7726-4710-a249-f126027c402e | RivrCoin | RIVR | 2014-07 | 7200 |
------------------------------------------------------------------------------------------
Although, looking at those results, I see that we need to expand the query to include the label of the p2p protocol used by the coin: PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?node ?label ?symbol ?protocol ?incept ?bt WHERE {
?node skos:prefLabel ?label .
?node doacc:incept ?incept .
?node doacc:symbol ?symbol .
?node doacc:protocol ?p .
?p skos:prefLabel ?protocol .
?node doacc:block-time ?bt .
FILTER (?incept > "2013-12" && ?bt > 300)
} order by ?bt
that's better ...
-------------------------------------------------------------------------------------------------------
| node | label | symbol | protocol | incept | bt |
=======================================================================================================
| doacc:Dbe503204-7558-4362-94fb-d0fde4998b3a | Bulbcoin | BULB | bitcoin | 2014-08 | 380 |
| doacc:D0d94412d-27fd-4326-957e-a192e34254c0 | DiamondBack | DBK | cryptonote | 2014-08 | 384 |
| doacc:D9d7c7700-a2cb-40c4-aa52-859ad80bbf8e | 419coin | SCAM | bitcoin | 2014-04 | 419 |
| doacc:D52624384-c024-4497-b44f-e0a803c5923d | Pxlcoin | PXL | bitcoin | 2014-01 | 420 |
| doacc:Dee298eff-b026-4480-9a89-f70255f096c4 | Auroracoin | AUR | bitcoin | 2014-02 | 600 |
| doacc:D5a5921bb-6700-4a56-9bf6-558af5b2f7f7 | Arkhash | ARK | bitcoin | 2014-03 | 600 |
| doacc:D79ffc442-dddc-41da-822c-2f7fb4017f40 | BitcoinNEW | BTN | bitcoin | 2014-04 | 600 |
| doacc:D4f9acba8-77b5-4875-add3-4fe3da74c313 | Lemonadecoin | LEO | bitcoin | 2014-05 | 600 |
| doacc:Da47a45e7-540a-44cd-90df-b9c09d07c479 | Metalcoin | MTC | bitcoin | 2014-06 | 600 |
| doacc:Df73a7291-147f-4b6d-b04d-9a6e190b2e2c | Zippercoin | ZIP | bitcoin | 2014-06 | 600 |
| doacc:D0e92be0b-24a7-405c-9d7d-838e8de54a10 | BigBullioncoin | BIG | bitcoin | 2014-07 | 600 |
| doacc:Def44a8b7-1825-490c-a271-f4929ba94b9c | CherryNote | CRR | cryptonote | 2014-07 | 600 |
| doacc:D4c23219d-ead1-4a97-bea1-b1339ae8faaf | Eaglecoin | egc | bitcoin | 2014-07 | 600 |
| doacc:Da0770ce7-0c77-4295-b225-a54a277a7828 | SpreadCoin | SPREAD | bitcoin | 2014-07 | 600 |
| doacc:D61d7490f-b92a-4475-ba84-4fe5e929117d | ASDcoin | ASD | bitcoin | 2014-08 | 600 |
| doacc:D944be229-25c2-4569-971c-5ca8999ecf68 | Nostrum | NOS | node | 2014-09 | 600 |
| doacc:D944be229-25c2-4569-971c-5ca8999ecf68 | Nostrum | NOS | nostrum | 2014-09 | 600 |
| doacc:D88c5d412-9baa-4907-8408-c6c953ec122a | Asspenny | ASS | bitcoin | 2014-04 | 720 |
| doacc:Dfd347290-f43c-4172-94f6-8b31aa207fc4 | Spirecoin | SPIRE | bitcoin | 2014-02 | 900 |
| doacc:D4cd50334-925a-425e-8a63-e294c04e1f84 | Arkenstone | ARS | bitcoin | 2014-05 | 900 |
| doacc:Dbd5c4ce0-9e46-463b-b014-6181b605292c | Irccoin | IRC | bitcoin | 2014-04 | 1200 |
| doacc:D9cc029d2-3c3f-4741-a4fd-6928e5253a09 | EdisonX3 | EDISON | bitcoin | 2014-03 | 1800 |
| doacc:D72f28a0f-7726-4710-a249-f126027c402e | RivrCoin | RIVR | bitcoin | 2014-07 | 7200 |
-------------------------------------------------------------------------------------------------------
If you wanted to include only altcoins that use the bitcoin protocol, just add that constraint to the filter expression (you need to explicitly provide the @en lang spec to constrain the match to just the english strings, I now regret editing all the @en out of the results) FILTER (?incept > "2013-12" && ?bt > 300 && ?protocol = "bitcoin"@en)
Um, looks like a duplicate there for Nostrum, created when they switched the labels for their protocol, so I need to add a DISTINCT to the result spec ... PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT DISTINCT(?node as ?uuid) ?label ?symbol ?protocol ?incept
?node skos:prefLabel ?label .
?node doacc:incept ?incept .
?node doacc:symbol ?symbol .
?node doacc:protocol ?p .
?p skos:prefLabel ?protocol .
?node doacc:block-time ?bt .
FILTER (?incept > "2013-12" && ?bt > 300)
} order by ?bt
Continue refining until you've got what you need. HTH Cheers Graham |
|
|
|
Finally, here it is:
Nice. Does exactly what it says on the tin. I like the block spacing estimate, most useful. Cheers Graham |
|
|
|
Awhile back I started a list of altcoin exchanges, and thought I'd post it here because I was unable to find anything similar on bct.
I eventually realised that plaintext lists are less than useful and that bct isn't necessarily the best medium for publishing them, either. So Minki has her own listing which includes urls and other info ... http://minkiz.co/exchangeCheers Graham |
|
|
|
Yes, in PHP. I did not make this code to be public so it's crap and pretty messy, but if you want it here it is anyway:
Thank you, that's most helpful. Cheers Graham |
|
|
|
I thought similar to this, meaning: matching colors and style, and the home page is intended for this... for now I managed to do a simple job my self (that home page I did), First I was looking for something fancy.... but it is worth waiting a while. Well, the user's one and only task on this page is to find the right game button, that's all they'll see. Have you tried just using the same background image throughout? You might find that to be enough in terms of visual unity. Cheers Graham |
|
|
|
I have parsed the ANN topics ...
Programmatically? Source code available? (Nice work, BTW). Cheers Graham |
|
|
|
create a good looking home page and the design has to match the looking of the core theme.
If you can narrow that down a bit more, that'd be useful in trying to scope the task. Do you mean “echo”, as in “similar” or “match” as in “same”? The “I’ll know it when I see it” approach can often be a show-stopper for casual design jobs. Cheers Graham |
|
|
|
I am interested in an Alt-coin index of some sort or maybe an informational wiki on all contender alt coins. This would include:
Date established
Code Base
Open source details
Number, size of exchanges
Market cap
Trade volume
Mining strategy, mining outlook
Premine, other nefarious concerns
POS (proof of stake not piece of s***)
Developer community details - lead developer history, contributors
Proven technology advantages
Game plan for usage penetration in the real world
Non-dev community assessment (Reddit, facebook, bitcointalk, cell phones in Africa)
World domination spin
Why it won't work
Why it will work
I would be willing to donate bitcoin to get such an information page started.
Yeah, we're on it. We can't meet all of your requirements in terms of information spread and detail but we've made a start with DOACC (Description of a CryptoCurrency). DOACC is a(n inconsistent) collection of metadata for an extensive range of altcoins. The metadata is persisted as an RDF graph, self-describing with the aid of an accompanying OWL ontology: ( https://github.com/DOACC/doacc). The index currently runs to a total of 1550+ entries: ( https://github.com/DOACC/individuals) and rising relentlessly, ofc. The dataset is intentionally highly amenable to further processing. For example, we present a user-friendly version on Minkiz (ninja launch mode, see sig.) and offer a SPARQL endpoint for querying the dataset. For example, this SPARQL query: PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?node ?label ?symbol ?incept WHERE {
?node skos:prefLabel ?label .
?node doacc:symbol ?symbol .
?node doacc:incept ?incept .
?node doacc:protocol ?prot .
?prot skos:prefLabel "cryptonote"@en
} ORDER BY ?incept ?symbol
pasted into the form field here: http://minkiz.co/sparql will return a list of all the altcoins that use the cryptonote protocol. ... optionally in JSON. I'll just dump the results here by way of illustration, just stand back a little further, if you would ... {
"head": {
"vars": [
"node",
"label",
"symbol",
"incept"
]
},
"results": {
"bindings": [
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-04"
},
"label": {
"type": "literal",
"value": "BitMonero",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#D714a2b9a-1c99-4dcc-b733-982e43d70cbe"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "BMR"
}
},
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-04"
},
"label": {
"type": "literal",
"value": "Monero",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#Dcc87ddf9-d138-48d4-ab89-18f36c6fb5b9"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "XMR"
}
},
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-05"
},
"label": {
"type": "literal",
"value": "Fantomcoin",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#D24204952-b71b-414e-9728-014258fb916a"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "FCN"
}
},
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-05"
},
"label": {
"type": "literal",
"value": "MountCoin",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#D69f0628a-c8f3-4583-9bac-fbcbb8db4122"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "MNT"
}
},
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-05"
},
"label": {
"type": "literal",
"value": "QuazarCoin",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#D24d3f414-6bc9-4a89-a1a0-724122c08e26"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "QCN"
}
},
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-06"
},
"label": {
"type": "literal",
"value": "MonetaVerde",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#D563f9b93-4dfc-498c-967f-c2a621847e92"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "MCN"
}
},
{
"incept": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "2014-07"
},
"label": {
"type": "literal",
"value": "Dashcoin",
"xml:lang": "en"
},
"node": {
"type": "uri",
"value": "http://purl.org/net/bel-epa/doacc#D8eb61f7d-b494-46ee-ae03-0adf90aa44d9"
},
"symbol": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"type": "typed-literal",
"value": "DSH"
}
}
]
}
}
Obviously, that's not the full roster. I'm in the middle of a sizeable update, backfilling a few dozen altcoins that we missed recently. We're using Minkiz to present the data sliced and diced, for example; a pair of lookup tables for names to symbols and symbols to names. We also provide in-depth support for hodlers via the HodlerScope but that may not be the kind of analysis you seek If you're prepared to re-examine your wish list and pare it down to a set of practicalities (e.g. swapping out four paras of rambling opinion in favour of a rating of 1-5 on the "does it smell okay?" scale and similar value-enum array choices) then we could be in business. Cheers Graham |
|
|
|
i can also confirm kingscrown account is real and he is the one behind it.
guy is preety known in altcoin scene i will be investing in this soon when i get few BTCs. its a sure win IMO.
... I have a preety good network of friends here and there.
Thanx also preety good member vouch for me being fair + there is escrow here and more news coming.
That's a preety rare acoustic confusion. Cheers Graham |
|
|
|
We have already hired a developer and gave him an advance payment in the amount of 1 BTC.
If anyone wants to try this fix (straightforward, AFAICT. The original dev was a bit lax with the search/replace) ... https://github.com/gjhiggins/equinoxcoinI've got a couple of nodes connected but no access to a blockchain. If someone with a Linux box and a recent blockchain wants to compile up the above fixes, we could have a go at unsticking the blockchain: Cheers Graham |
|
|
|
I suppose we like the idea.
And some of us don't think it's had a decent chance to prove its merit. I see altcoin space as feature-oriented. To take a deliberately jaundiced perspective: it's all just a pile of whistles and bells decorating classic bitcoin - the basic feature set is fixed by the fork parent. In that context, PoB is a potential genuine extension of that feature set and has some claimed merit - this we are checking out because if it can be made to work, it gives the coin a valuable USP. The idea does seem to make sense, at least at a surface level and I guess we're big enough and ugly enough to want to persist in finding out whether it is actually capable of delivering. Maybe the dev didn't get the initial implementation quite right. It's not as if it's the first time that's happened. A few competent people could always take over.
I agree with the dev's assessment, a revised implementation based on the Peerunity fork holds some promise. The current slimcoin implementation is based on the Bitcoin 0.7.3 codebase (from which Peercoin was originally forked) and that's possibly a bit of an unsteady reed, still using BerkeleyDB and missing a raft of subsequent bugfixes, tweaks, etc. Ironically, the collective task of getting this particular p2p engine firing smoothly is helping to establish a stronger sense of community ownership. Whilst it's not a strategy one would necessarily choose if given the option, there's little sense in throwing away all the progress to date in an impatient hissy-fit. I prefer to provide support where I think it'll be most effective, even if it's merely contributing a reliable node, as in this instance. I'm not at all sure that the effect of the last round of fixes wasn't banjaxed by the seed nodes going down while the dev was on holiday. We're still regaining network stability and that seems to be a problem in principle for any relatively low-hashrate coin. We shouldn't underestimate the amount of work involved here. A browse through the repos commit history will inform you that “John Smith” has been consistently and persistently working on the code since December last year. The kids have only just gone back to school and his last post was about three weeks ago. I'm not anticipating full-time commitment from a man with a family, that would be unreasonable and, by my lights, undesirable. However, I do think that the basic initial promise has been kept - mining on a Raspberry Pi and I prefer not to lose sight of this original goal because I can see a nice little brand story (“marketing strategy”, if you like) that would position this coin rather prettily in the spectrum of altcoin offerings and while it wouldn't necessarily demand involvement from the community of Slimcoin miners/owners, I believe it would definitely invite it. If-and-when the boat stops rocking, I'll start developing the idea further. Cheers Graham |
|
|
|
Just for confirmation: gjh@tessier:~/Projects/Coinage$ ./slimcoin/src/slimcoind getblockhash 90141
00000010e9815d44f9f3e3dcba3ad793a8f81d9bf28498c81d83aed28b30d3b9
Cheers Graham |
|
|
|
Just a pointer to our candidate for a list of all altcoins, if anyone's interested ... DOACC (Description of a CryptoCurrency) is an exhaustive collection of altcoin metadata. The collection currently has data for a total of 1536 altcoins. It's maintained in a Github organisation repos: https://github.com/DOACCand published as an RDF graph of ntriples, amenable to further processing https://github.com/DOACC/individuals(There's also an OWL ontology for the domain and an accompanying collection of coin logos.) We also publish it as browsable Linked Open Data (well, that's the intention, as soon as the boat's stopped rocking): http://minkiz.co/lodand provide a SPARQL endpoint for querying the graph: http://minkiz.co/sparqlas well as handy-to-navigate lists: Name->Symbol lookup: http://minkiz.co/coin/name/ Symbol->Name lookup: http://minkiz.co/coin/symbol/And if you just want to browse, there's a one-page iliiustrated listing: http://minkiz.co/coin/Cheers Graham |
|
|
|
try one of the following IP's, my client is connected mostly with them.
85.10.194.50
66.254.112.14
78.189.29.211
^^^ That's our server. I have the wallet on my laptop synched to it (and others) and minting seems to be happening --- and being confirmed, unlike the previous coupla dozen in late August which weren't. As to whether this is the right blockchain, well it's a popular choice of blockheight is all I'll venture gjh@tessier:~/Projects/Coinage$ slimcoin/src/slimcoind getpeerinfo
[
{
"addr" : "146.185.168.142:43250",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409943929,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "222.190.105.10:47587",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409943931,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "66.228.43.203:45956",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409943933,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "54.191.247.114:56697",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409943993,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88889,
"banscore" : 0
},
{
"addr" : "78.189.29.211:41682",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019555,
"conntime" : 1409944101,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 15164,
"banscore" : 0
},
{
"addr" : "66.254.112.14:41682",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410018872,
"conntime" : 1409944261,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 15157,
"banscore" : 0
},
{
"addr" : "202.198.62.133:37858",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409944490,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "85.234.11.66:58836",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409944494,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 15164,
"banscore" : 0
},
{
"addr" : "144.76.118.179:44376",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409944496,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "106.186.126.57:41179",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019597,
"conntime" : 1409944507,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "83.104.61.47:23340",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409944511,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "188.134.72.213:37708",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409944511,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "95.211.57.109:53259",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409944512,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "49.77.54.36:49985",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409944514,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88887,
"banscore" : 0
},
{
"addr" : "192.3.21.71:32920",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019597,
"conntime" : 1409944543,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88890,
"banscore" : 0
},
{
"addr" : "121.229.79.242:26211",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409944543,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88890,
"banscore" : 0
},
{
"addr" : "192.99.184.33:35578",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409944549,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88890,
"banscore" : 0
},
{
"addr" : "106.186.126.61:53919",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019597,
"conntime" : 1409944555,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88892,
"banscore" : 0
},
{
"addr" : "54.191.21.109:62810",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019597,
"conntime" : 1409944562,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 15157,
"banscore" : 0
},
{
"addr" : "222.94.98.239:55567",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409944631,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88892,
"banscore" : 0
},
{
"addr" : "60.28.18.130:58278",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409944680,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 88892,
"banscore" : 0
},
{
"addr" : "88.113.158.141:57544",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1409975501,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89230,
"banscore" : 0
},
{
"addr" : "112.113.96.138:50758",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1409997486,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89479,
"banscore" : 0
},
{
"addr" : "79.194.74.153:60166",
"services" : "00000001",
"lastsend" : 1410019599,
"lastrecv" : 1410019599,
"conntime" : 1409999014,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89516,
"banscore" : 0
},
{
"addr" : "81.207.93.95:51027",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1410004369,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89558,
"banscore" : 0
},
{
"addr" : "200.50.125.123:57248",
"services" : "00000001",
"lastsend" : 1410019100,
"lastrecv" : 1410019099,
"conntime" : 1410011674,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 46501,
"banscore" : 0
},
{
"addr" : "190.252.87.227:49461",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019414,
"conntime" : 1410013361,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 15164,
"banscore" : 0
},
{
"addr" : "107.181.250.216:63620",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410015262,
"conntime" : 1410015262,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 75468,
"banscore" : 0
},
{
"addr" : "85.57.241.211:3585",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410017695,
"conntime" : 1410015630,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 46470,
"banscore" : 0
},
{
"addr" : "85.58.54.90:3584",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410015836,
"conntime" : 1410015836,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 15164,
"banscore" : 0
},
{
"addr" : "177.80.48.195:52070",
"services" : "00000001",
"lastsend" : 1410018372,
"lastrecv" : 1410018386,
"conntime" : 1410016050,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 49996,
"banscore" : 0
},
{
"addr" : "118.100.200.159:51528",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019597,
"conntime" : 1410016269,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 15164,
"banscore" : 0
},
{
"addr" : "119.56.126.18:18854",
"services" : "00000001",
"lastsend" : 1410019598,
"lastrecv" : 1410019598,
"conntime" : 1410016307,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89679,
"banscore" : 0
},
{
"addr" : "81.167.135.5:65127",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019597,
"conntime" : 1410017124,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89674,
"banscore" : 0
},
{
"addr" : "88.151.72.47:54044",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410019414,
"conntime" : 1410018223,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 15164,
"banscore" : 0
},
{
"addr" : "89.212.138.20:60792",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410018242,
"conntime" : 1410018235,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 47557,
"banscore" : 0
},
{
"addr" : "124.10.130.186:3043",
"services" : "00000001",
"lastsend" : 1410019597,
"lastrecv" : 1410018894,
"conntime" : 1410018894,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 42047,
"banscore" : 0
},
{
"addr" : "109.199.64.140:3051",
"services" : "00000001",
"lastsend" : 1410019199,
"lastrecv" : 1410019198,
"conntime" : 1410019197,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 39158,
"banscore" : 0
},
{
"addr" : "188.34.255.94:49935",
"services" : "00000001",
"lastsend" : 1410019509,
"lastrecv" : 1410019503,
"conntime" : 1410019374,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 52525,
"banscore" : 0
},
{
"addr" : "112.113.96.138:52516",
"services" : "00000001",
"lastsend" : 1410019389,
"lastrecv" : 1410019599,
"conntime" : 1410019385,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 89719,
"banscore" : 0
}
]
Be careful out there! Cheers Graham |
|
|
|
I wish I hadn't mentioned it now. A not-so-cursory second glance reveals some tell-tale warning signs, not the least of which is the grammar/spelling step change in the OP's post history (sigh). None of the mentioned names/handles of the team resolve. ICO raised 0.00000000 BTC, OP fell silent on 25th, the planned launch of 29th didn't happen. Cheers Graham |
|
|
|
most concerned with transaction speed and stability. A coin that you could use for point of sale and not worry about forks
If you want a PoW-protected ledger, AFAICT the most solid path currently would be a full-history fork of the latest Bitcoin Core 0.9.x, configured to use BLAKE2 throughout for hashing ... or, if you're concerned about best performance on pos-grade kit, browse the performance graphs, make your own selection. Cheers Graham |
|
|
|
- What do you expect?
- What do you need?
- What you experience, and what's your relationship with myrdiacoin?
- What are the risks when it comes to the same hard fork and changing the code base for ltc
To be fair to Ahmed, answers to all these questions are readily available (I know, because I have availed myself of them). Here I am waiting to speak gjhiggins, a person deemed to be involved in the very recent advances q2c.
I have already made a recommendation that Qubitcoin users/miners accept Ahmed's offer (the alternative is to drum up enough resources to commission him to implement it at some later date). My assessment was based on the economic and technical pressures on Qubitcoin. They haven't changed, nor has the recommendation. Apologies for not responding to your PM. At the moment, I am necessarily totally focused on revenue and the unfortunate fact is that a single day's pay for contract work, if exchanged for Qubitcoin, would catapult me to the upper ranks of the rich list. The inescapable fact is that I simply can no longer afford to devote significant amounts of time to developing Qubitcoin. But this is to Qubitcoin's ultimate benefit, it's a p2p network and that's how it was designed to work, not merely be a charitable hobby project for some fortunately well-resourced individual. I stepped into what I consider to be a temporary breach; a krecu returning with hair-raising tales of everyday life in a war zone would be welcomed with open arms. Go on, tell me I'm wrong, I dare ya --- see, there is a genuine sense of community but it needs nurturing. The real onus is on the Quibitcoin-owning community to operate as a thriving p2p network. I have made a number of contributions in an attempt to sustain interest in the interim and they have indeed apparently been well-received. Qubitcoin does still seem to have some potential but the community is undecided on how to proceed. I originally misperceived this inertia as a simple variant of “bystander apathy” but after looking more closely I now realise it is more deep-seated and pragmatic in its origins and I suspect it's shared by nearly all similar altcoins. (This isn't the appropriate forum for a detailed explanation of the social psychology of online groups of investors and providing a trivial description of the issues would necessarily oversimplify things and would risk triggering profoundly damaging misperceptions.)I strongly suggested that someone, anyone, organise a vote. Nothing happened. We Brits have a saying: “You can lead a horse to water but you can't make it drink” and it is very pertinent in this case. Stability deriving from inaction-by-default is a feature that's explicitly wired in to the fundamentals of the bitcoin protocol. It is how it is supposed to work. Granted, it may not necessarily be working to Qubitcoin users'/miners' long-term interests in this particular case but that's just my opinion and ... as I have noted previously ... I have no skin in the game and thus not in a position to gainsay the opinions of those who do. tl;dr bearing in mind that advice is worth what you pay for it: either take Ahmed's offer or get yourselves sorted out for ponying up enough $$ ( not Q2C) to support the hash rate later if that turns out to be an issue. It's all about gaining personal advantage from incisive and accurate risk assessment --- that's what brings y'all here, right? Cheers Graham |
|
|
|
|
Show Posts
