YoBits now listing altcoins released without source? Wow, you guys are gluttons for risk. Cheers Graham How can Yobit list a coin without source ? Of course they have source ! Care to share the location of the source code or are you just expressing an opinion? Cheers Graham |
|
|
|
YoBits now listing altcoins released without source? Wow, you guys are gluttons for risk. Cheers Graham |
|
|
|
Fixed the fix. I couldn't help but laugh at myself for a while.
Fix is fixed: [wallet 9MUf87]: transfer 3 9EjUxnMqY8AXaCkVUwqfsDQKPyDdVquM1SP5s1kw9D7tbK44KCCUAU8eTLZHDjzv66K15TxSYZ1SwAqjxR12ZXL76NTUDzC 10 -f 0.001
Money successfully sent, transaction 10382a6bfbbc22616ed7059e1e1ba9e175c612b2f6b0ff542c26a1fd0fec7f55
[wallet 9MUf87]:
Cheers Graham |
|
|
|
TO SEND A TRANSACTION ON WINDOWStransfer 3 (lets keep this as a standard) ADDRESS_HERE AMOUNT_HERE -f FEE My curiosity is piqued, any chance of an explanation of why three is a good number to use as standard? I'd also be grateful for a pointer that leads to information on how to calculate the fee. Cheers Graham |
|
|
|
I got it from wallhaven, images are public domain. With public domain images you're free to use them in any way.
Er, just because an arbitrary web site spuriously declares it to be public domain doesn't make it so, they have no right to make that assignment. The image owner is Tokyo Fashion, the image rights are clearly stated on the flickr page: “All rights reserved”. That's not public domain by any stretch of the imagination. Cheers Graham Not necessarily.... Check the precedent here https://en.m.wikipedia.org/wiki/Cariou_v._PrinceThanks for drawing my attention to that, I wasn't aware the appeal had succeeded. Not that it negates the point I made. Prince was fully aware of the image rights whereas OP was labouring under a profound misapprehension that the work was in the public domain and could be freely adapted and re-used. OP would most likely lose this argument, but as long as he is t selling it he might be safe. The original copyright holders might not care, at worst would send a cease and desist.
I agree but s'not so much the current instance, more a case of helping someone avoid easily-avoidable trouble in the future. I would imagine Tokyo Fashion would've responded positively if the OP had sought permission and a “by kind permission” would lend just a bit more weight to the work. The web-served versions of our own works are freely available for non-commercial re-use. An example:  They're available as limited-edition prints, we're looking at using the blockchain for provenance. Cheers Graham |
|
|
|
I recently won a contest, and I won 750$ funds in my Vultr account  Applause! So I am willing to use my vultr funds to contribute a dozen block explorers for a whole year.
Very public-spirited of you ... $62.50 will get you a reasonably capable machine. If I were you, I'd be looking at RPC-ACE (php) or one of the open source explorers based on node.js such as Iquidus that read the metadata via the RPC port (with the attendant caveats about inspecting the coin source before taking the RPC output on trust, there have been examples where crooked devs have hacked their coin's RPC code in order to mask a hidden premine). Abe, the original Python-implemented explorer actually reads the metadata direct from the blockchain and stores it into an RDBMS, so is correspondingly more challenging to set up but has the advantage that it is very difficult, even impossible to fool it into reporting false values. It has fewer features than the more recent explorers based on node.js. This might also help: https://bitcointalk.org/index.php?topic=1080718.0Cheers Graham |
|
|
|
Through our roadmap, we may start having a GUI wallet that will most probably solve most of your design issues.
Noted, thanks. The project is flagged as an educational exercise; I predict that one pedagogical outcome will be the rediscovery of the oft-encountered phenomenon that UI cannot successfully be bolted on afterwards. the list of transfers has predictably become unwieldy Does this mean you were able to successfully send coins? Gah, faked out by UI inconsistency (“list_transfers” (verb+noun) vs “incoming_transfers” (compound noun)). I meant “incoming transfers”, the “list transfers” is equally unwieldy but does offer a lot more in terms of information, so no, I haven't sent coins. Actually, I did just try. [wallet 9MUf87]: transfer 9EjUxnMqY8AXaCkVUwqfsDQKPyDdVquM1SP5s1kw9D7tbK44KCCUAU8eTLZHDjzv66K15TxSYZ1SwAqjxR12ZXL76NTUDzC 10
Error: mixin_count should be non-negative integer, got 9EjUxnMqY8AXaCkVUwqfsDQKPyDdVquM1SP5s1kw9D7tbK44KCCUAU8eTLZHDjzv66K15TxSYZ1SwAqjxR12ZXL76NTUDzC
I read the help line transfer <mixin_count> <addr_1> <amount_1> [<addr_2> <amount_2> ... <addr_N> <amount_N>] [-p payment_id] [-f fee] - Transfer <amount_1>,... <amount_N> to <address_1>,... <address_N>, respectively. <mixin_count> is the number of transactions yours is indistinguishable from (from 0 to maximum available)Trouble is, I've no real idea what the terms mean and it's not at all clear what I would need to learn in order to construct a successful xfr: [wallet 9MUf87]: transfer 0 9EjUxnMqY8AXaCkVUwqfsDQKPyDdVquM1SP5s1kw9D7tbK44KCCUAU8eTLZHDjzv66K15TxSYZ1SwAqjxR12ZXL76NTUDzC 10
Error: Internal node error
Chicken and egg, unless the UI is brought back to a realistic level of difficulty, the userbase will be confined to those who have a compelling motivation to master the inherent technical challenge. But as I mentioned, I'm ignorant of the project objectives and this may not be a design concern. Cheers Graham |
|
|
|
Have you tried restarting? And when you did did it persist?
Sorry, transient grump. Props for a prompt response. Restarted, no sign of repeat thus far, will let it run and report any further instances. Minor UI grumbles, command line editing is sub-par for a money-critical app; the list of transfers has predictably become unwieldy, desperately needs a range limit; showing a datetimestamp for each transfer in the list is probably crucial (okay it is available via reconciling the data with the log file but that's not exactly user-friendly). OTOH, I'm ignorant of the project objectives, so perhaps user-friendliness isn't a design parameter, if so ignore the above grumbles. Cheers Graham |
|
|
|
fwiw ... Was running a node and solomining: $ tail Tavosd.log
2015-Jul-18 06:44:50.191572 [miner 2]Found block for difficulty: 139359
2015-Jul-18 06:52:44.858187 [P2P5][46.72.126.178:17581 INC] SYNCHRONIZED OK
2015-Jul-18 06:52:44.864038 [P2P0][46.72.126.178:17451 OUT] SYNCHRONIZED OK
2015-Jul-18 07:05:16.594935 [miner 1]Found block for difficulty: 142652
2015-Jul-18 07:08:33.605382 [miner 0]Found block for difficulty: 144061
2015-Jul-18 07:36:17.692821 [P2P6]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 891
id: <19f32b105bbdd724bba0459e0224756c60d090daf421a50724dea7d8dd4a314c>
PoW: <55ba3c632e965104a333e93d98029031430d7eb31ed973d671e6aeeca4050000>
difficulty: 151175
2015-Jul-18 07:46:36.586413 Failed to read line. Stopping...
I've left it stopped. Cheers Graham |
|
|
|
I got it from wallhaven, images are public domain. With public domain images you're free to use them in any way.
Er, just because an arbitrary web site spuriously declares it to be public domain doesn't make it so, they have no right to make that assignment. The image owner is Tokyo Fashion, the image rights are clearly stated on the flickr page: “All rights reserved”. That's not public domain by any stretch of the imagination. Cheers Graham |
|
|
|
I'm getting lazy and have developed a tendency to rely on others’ write-ups of the insights: “The final challenge which many traditional blockchains face is that due to their public nature, many will simply not be able to work without an anti-spam mechanism of some sort. The anti-spam mechanism used by most blockchains is that data which is to be stored in the blockchain must be accompanied by some payment or deposit of the blockchain’s built-in token. This creates a “pay-to-play” atmosphere which suits those individual nodes who possess a significant amount of the tokens well, but may not suit those individuals who do not possess the tokens. Indeed, this is an insurmountable problem for many blockchains and outside of “wealthier” users subsidizing others so that they might benefit from the utility of whatever function that blockchain is meant to provide, there is no answer.”
- https://erisindustries.com/products/erisdb/A couple of observations: i) “may not suit” is unnecessarily timid, “ will not suit” is much more like it and ii) note and inwardly digest: “insurmountable problem ... no answer” Cheers Graham |
|
|
|
Claro. The work I described is taking place in a different repos, I erroneously assumed you were using that one. Thanks for the heads-up. Cheers Graham |
|
|
|
|
Website states: TOTAL SUPPLY: 20,000,000 iBits
ANN states: SUPPLY: 61,800,000
Which is it?
Cheers
Graham
|
|
|
|
Looks promising !
The new source code is not compiling for me:
tl;dr - Which branch are you using? Thanks for the kind words. There isn't a release per se of the new source code of VCoin for Core 0.11, sorry about that. It's testnet-only anyway atm because of the post-0.9 backwards-incompatible protocol changes. Publicly available code for a working VCoin 0.11 node would likely cause a fork and irrevocably separate 0.11 and 0.8 clients, so any release will need to be planned, advertised and carefully managed so that exchanges, pool operators and users of 0.8 clients are given adequate support in upgrading. The repos is somewhat teeming with branches atm, I need to get a sense of what's worth including and adding to the maintenance load and what isn't. The additional functionality (and any associated structural change) is separated out into individual branches, enabling me to manage the dependencies more effectively. When we're ready, I'll merge what's actually wanted and cut a release. In the interim, I'll take a look at the “pre-release” branch and try to ensure that it compiles. Cheers Graham |
|
|
|
i shut down my node, have not checked on sic in a while, obviously some people are still mining it but although for a while i thought it was a sleeper , i guess it would have woke up by now if it was ever going to
Thank you for travelling SIFcoin, we hope you had an enjoyable journey. I see things differently and will be maintaining the Minkiz SIF node and the ACME explorer for the foreseeable future. Cheers Graham |
|
|
|
A short progress report- a “getwork” branch created - with half a view to reintegration with 0.11 at some point, if it looks feasible
- an “inscribe” OP_RETURN branch created (see screenshot), enabling a “public reference” (a resolvable RDF Graph URI) to be permanently inscribed on the blockchain, code adapted from Grandpa Jones' Synergy
Porting code from an 0.8 base is agonisingly slow work ... but is still a lot faster than coding from scratch (when the edit-compile-debug cycle time is taken into consideration).  (Screenshot is of wallet running in Qt IDE debug, connected to testnet3 network). Cheers Graham
|
|
|
|
Is the a chronological list anywhere for alts as they were released. Some of the first 100 coins must have tiny mintings. Some were disregarded almost at launch.
There's a website dedicated to this... Sort of yes ... and no. I have data, some of it is inaccurate. There is a website ( https://minkik.co/coin/) that presents some serialisations of altcoin metadata but atm there's no chronological listing. More specifically; I maintain DOACC, a collection of metadata about released/mooted altcoins: https://github.com/DOACC. The metadata is maintained as an RDF graph with a couple of associated OWL ontologies in support. Every altcoin recorded in DOACC has an “incept date” (a YYYY-MM value), name, symbol, distribution scheme, protection scheme, algo and block time. A minimalist SPARQL query would be: PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?label ?d WHERE
{
?node skos:prefLabel ?label .
?node doacc:incept ?d .
}
ORDER BY ?d LIMIT 100
which produces the result (lightly edited for readability) : | Bitcoin | 2009-01 | | Freicoin | 2011-02 | | Namecoin | 2011-04 | | iXcoin | 2011-05 | | SolidCoin | 2011-08 | | Tenebrix | 2011-09 | | GeistGeld | 2011-09 | | I0Coin | 2011-09 | | RuCoin | 2011-09 | | Fairbrix | 2011-10 | | SolidCoin2 | 2011-10 | | Litecoin | 2011-10 | | BitChips | 2011-11 | | CoiledCoin | 2012-01 | | Realpay | 2012-02 | | Microcash | 2012-04 | | Timekoin | 2012-06 | | BBQCoin | 2012-07 | | Bytecoin | 2012-07 | | Starcoin | 2012-07 | | ZcCoin | 2012-08 | | Peercoin | 2012-08 | | TerraCoin | 2012-10 | | Vertcoin | 2013-01 | | Novacoin | 2013-02 | | SmallChange | 2013-04 | | Bytecoin | 2013-04 | | Feathercoin | 2013-04 | | Sexcoin | 2013-05 | | SunRiseCoin | 2013-05 | | EZCoin | 2013-05 | | Powercoin | 2013-05 | | barcoin | 2013-05 | | Porncoin | 2013-05 | | DragonCoin | 2013-05 | | Weedcoin | 2013-05 | | Hypercoin | 2013-05 | | Mincoin | 2013-05 | | Bitgem | 2013-05 | | GameCoin | 2013-05 | | Fastcoin | 2013-05 | | Elacoin | 2013-05 | | SuperCoin | 2013-05 | | RoyalCoin | 2013-05 | | UScoin | 2013-05 | | Vaginacoin | 2013-05 | | AmericanCoin | 2013-05 | | Digitalcoin | 2013-05 | | Fastcoin2 | 2013-05 | | Franko | 2013-05 | | Luckycoin | 2013-05 | | Phoenixcoin | 2013-05 | | Ripple | 2013-05 | | Memecoin | 2013-05 | | Phenixcoin | 2013-05 | | Doubloon | 2013-05 | | Molecule | 2013-05 | | OneCoin | 2013-05 | | Megacoin | 2013-05 | | BitBar | 2013-05 | | Yacoin | 2013-05 | | JunkCoin | 2013-05 | | WorldCoin | 2013-05 | | Nibble | 2013-05 | | SkyCoin | 2013-05 | | Nanotoken | 2013-06 | | ZenithCoin | 2013-06 | | Quantumcoin | 2013-06 | | FlorinCoin | 2013-06 | | Anoncoin | 2013-06 | | YbCoin | 2013-06 | | Emerald | 2013-06 | | OnelastCoin | 2013-06 | | Krugercoin | 2013-06 | | 6Coin | 2013-06 | | RedCoin | 2013-06 | | GlobalCoin | 2013-06 | | Noirbits | 2013-06 | | Richcoin | 2013-06 | | LiquidCoin | 2013-06 | | XenCoin | 2013-06 | | Cryptogenic Bullion | 2013-06 | | Copperlark | 2013-06 | | Orbitcoin | 2013-06 | | Sifcoin | 2013-06 | | Flashcoin | 2013-06 | | Cryptobits | 2013-06 | | Quickcoin | 2013-06 | | IceCoin | 2013-06 | | Nucoin | 2013-06 | | Diamond | 2013-06 | | MasterCoin | 2013-06 | | ValueCoin | 2013-06 | | Infinitecoin | 2013-06 | | Cosmoscoin | 2013-06 | | Curecoin | 2013-06 | | RealCoin | 2013-06 | | Bottlecaps | 2013-06 | | TradeCoin | 2013-06 | | Primecoin | 2013-07 |
It is theoretically possible to establish a precise datetime for each altcoin's incept by consulting the datestamp of the coin's genesis block. This is, ofc, left as an exercise for the reader.As a courtesy to clients, Minkiz offers a SPARQL endpoint: https://minkiz.co/sparql (please don't abuse the endpoint, feel free to run your own Fuseki instance). Here's a canned version of the SPARQL query that takes you straight to the unedited SPARQL results. Good news/Bad news Dept: There is documentation for DOACC ... unfortunately it's impenetrable (I suspect). My original wheeze to use the Github project's “Git pages” to host the docs was scuppered by the js demands introduced by animating the examples and so I've parked the docs in a corner of Minkiz for the time being: https://minkiz.co/doaccdoc/index.html. (No apologies for the self-signed CA, get our CA root cert from http://bel-epa.com/X509/ --- DYR courtesy The Internet Archive.) HTH Cheers Graham Edit: added note about documentation |
|
|
|
Think I'm going to try to buy 1000 each or so of a bunch of super super cheap alt coins and just hope it goes the way of btc.  Good news! There's a lot of choice: https://minkiz.co/coin/Have fun. Cheers Graham (for the raw data, see http://github.com/DOACC) |
|
|
|
|
Show Posts
