No source code available. Not a good sign. Cheers Graham |
|
|
|
Sorry if you find this offending. I only seek more info and opinion of multiple people regarding the company. Not promoting anything or harassing anyone.
The company is registered in Malta. English is one of the two official languages of Malta. The text on the company website has multiple misspellings, indicating that English is not the author's native language. Conclusion: unforced error, falls well below acceptable commercial standards, amateurs masquerading as professionals, would not touch with a 20' bargepole. Cheers Graham |
|
|
|
If you are interested in joining such a list, please respond.
I'm interested in joining. Cheers Graham (Higgins, gjh@bel-epa.com) |
|
|
|
2. The Karmacoin logo is actually direct from the givekarma.net website and one of the only high quality Karma logos I can find
Okay, it was the “Karmacoin” text I was referencing but if that's an integral part of a raster image, I understand. From a graphic designer's perspective, ideally they'd get a scalable version of the graphic and a font name. Dunno about the latter but I created a PR for an SVG version of the coin logo. https://github.com/karmateam/karma/pull/5/commitsHTH. Cheers Graham |
|
|
|
The Bitcoin core wallet is a convoluted mess, if I had a spare 6 months I'd throw the lot of it away and start from scratch. In python.  That's all that's needed for a promising, high-appeal ICO  When do we start? Cheers Graham |
|
|
|
have had the below designed
Just a couple of minor points: 1. ask the designer to move the logo down a smidgen so that it's clear of the punched hole 2. I believe the convention is for just “Karma” now, rather than the old-style “Karmacoin” Overall impression: good quality merchandise, nicely designed, very likely to be well-received. Cheers Graham |
|
|
|
FYI
The security certificate must be self-signed? It comes up as unsafe, keep away, etc, with Chrome.
Absolutely self-signed. Have had an X.509 cert since forever. Always been a PITA, one cert per IP address, glad to use SNI with GnuTLS. If Chrome's nannying gets too much for you, d/l the CA here: https://bel-epa.com/X509/, fingerprint 33 F7 CD 33 D5 31 31 72 2B AF FE 4C 86 64 28 38 E0 B2 01 41 Yes, bel-epa is my domain too, archive.org's earliest entry: http://web.archive.org/web/19970416033248/http://www.bel-epa.com/Ohhh, memory lane ... http://web.archive.org/web/19961029160449/http://www.avonibp.co.uk/So, next year, I'll have been publishing on the web for 20 years continuously. Doesn't time fly. (The earliest footprint of mine that I can find is from usenet in '88) Cheers Graham |
|
|
|
Why 0.11? Primarily because 0.10 embraces P2SH addresses:
A somewhat better primary reason: 0.11 is the first version of Bitcoin Core to have the 80-byte OP_RETURN as default. 80 bytes allows full SHA256 hashes to be stored as “additional data” on the blockchain. Have you an electronic document/image/dataset that you want date- and/or content-stamped? Generate a hash of the item and inscribe the hash on the blockchain. Coinspark offer the service: http://coinspark.org/
Not unrelatedly, TIL about Time-Lock Encryption: Time-lock encryption is a method to encrypt a message such that it can only be decrypted after a certain deadline has passed. A computationally powerful adversary should not be able to learn the message before the deadline. However, even receivers with relatively weak computational resources should immediately be able to decrypt after the deadline, without any interaction with the sender, other receivers, or a trusted third party. from: “How to Build Time-Lock Encryption” - Tibor JagerWe propose a new time-release protocol based on the bitcoin protocol and witness encryption. We derive a “public key” from the bitcoin block chain for encryption. The decryption key are the unpredictable information in the future blocks (e.g., transactions, nonces) that will be computed by the bitcoin network. We build this protocol by witness encryption and encrypt with the bitcoin proof-of-work constraints. The novelty of our protocol is that the decryption key will be automatically and publicly available in the bitcoin block chain when the time is due. from “Time-release Protocol from Bitcoin and Witness Encryption for SAT” - Jia Liu and Flavio Garcia and Mark RyanCheers, Graham |
|
|
|
Prolly not, I implemented something similar in Python: https://minkiz.co/acmeFwiw, I maintain an RDF graph of the blockchain, tx, addresses and all. Is handy for ad hoc SPARQL querying. If I ever get the resources, I'll publish it as Linked Open Data. Cheers Graham |
|
|
|
No those are not all mine, just a random selection for demonstration purposes.
I'd be concerned that the possessive “mine” is a little too confusable with the verb. Cheers Graham |
|
|
|
You have stated that I work closely with someone you have proof is a scammer. You now need to:
No you are making this up! Where do I indicate he is a scammer? He doesn't scam, he works closely with people who scams for him (Digitalindustry, gustav and "friends" etc). What? “He doesn't scam, he works closely with people who scams for him” So they scam but he merely profits? You're making even less sense now. Don't you read what you write? ... "developers" who copy coins also have numerous accounts. An example was given above by me. In your opinion it is a bad example, and that is understandable because you work closely with him after reading your post history.
Right, back to business. 2. Post here all the posts from him to me and vice versa that you consider fall into the category of “work closely with”
If you don't, I will.
Ok that saves time for me. I only have seen your posts in Qubitcoin and Chaincoin so you can skip those posts. By the way, I am not interested so not sure for who you want to do it? And you don't have to convince me  . You're construing my posts to the chaincoin thread as “working closely with” the dev? That's a mischievous over-interpretation that verges on being deliberately disingenuous. And you seem to have something in your eye. I note that it was your post to the chaincoin thread that I previously encountered. That explains a lot. So if this is all the same person, I guess we can look forward to a Skeincoin upgrade next? That would be the logical follow-up to today's release of Chaincoin 0.8.9.15 https://bitcointalk.org/index.php?topic=422149.msg11674921#msg11674921Perhaps you should discuss the matter directly with the person you're accusing of operating more than one account and developing more than one coin. Cheers Graham |
|
|
|
In your opinion it is a bad example, and that is understandable because you work closely with him after reading your post history.
Okay-doke, enough with the sly innuendo. Let's have this out in the open where everyone can see it. You have stated that I work closely with someone you have proof is a scammer. You now need to: 1. Put a name to “him” 2. Post here all the posts from him to me and vice versa that you consider fall into the category of “work closely with” If you don't, I will. You did good work on the caveate emptor but you're way out of order here. And, while we're at it ... would you care to step out from behind the pseudonym and share your identity, home address and contact details? Cheers Graham Higgins |
|
|
|
Believe it or not; that post was a compliment.
I restrained an impulse to post a one-liner of my spontaneous applause but now that you bring it up explicitly, I can agree that it's a gem of a post. Cheers Graham |
|
|
|
I suppose that it's remotely possible your model is so impoverished that you genuinely don't realise your posts are badly misinformed, so much so that they are effectively indistinguishable from trolling: Chaincoin and Qubitcoin are dead for a long time. Even you don't bother anymore for those coins.
Wrong again. I lend a hand in curating a number of alts, some of which are listed here: https://minkiz.co/acmeSpecifically ... Welcome to the Chaincoin RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.
getpeerinfo
[
{
"addr" : "66.172.10.28:11994",
"services" : "00000001",
"lastsend" : 1434895580,
"lastrecv" : 1434895583,
"bytessent" : 504205,
"bytesrecv" : 1289494,
"conntime" : 1434702157,
"version" : 70001,
"subver" : "/Satoshi:0.8.99.11/",
"inbound" : false,
"startingheight" : 482126,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "5.9.56.229:11994",
"services" : "00000001",
"lastsend" : 1434895584,
"lastrecv" : 1434895583,
"bytessent" : 510189,
"bytesrecv" : 598320,
"conntime" : 1434702194,
"version" : 70001,
"subver" : "/Satoshi:0.8.99.14/",
"inbound" : false,
"startingheight" : 482126,
"banscore" : 0
},
{
"addr" : "37.59.24.15:11994",
"services" : "00000001",
"lastsend" : 1434895584,
"lastrecv" : 1434895584,
"bytessent" : 803105,
"bytesrecv" : 1395591,
"conntime" : 1434702238,
"version" : 70001,
"subver" : "/Satoshi:0.8.99.14/",
"inbound" : false,
"startingheight" : 482126,
"banscore" : 0
},
{
"addr" : "108.61.191.186:11994",
"services" : "00000001",
"lastsend" : 1434895583,
"lastrecv" : 1434895583,
"bytessent" : 725093,
"bytesrecv" : 598000,
"conntime" : 1434764690,
"version" : 70001,
"subver" : "/Satoshi:0.8.99.14/",
"inbound" : false,
"startingheight" : 482878,
"banscore" : 0
},
{
"addr" : "104.238.146.223:11994",
"services" : "00000001",
"lastsend" : 1434895581,
"lastrecv" : 1434895583,
"bytessent" : 63004,
"bytesrecv" : 50463,
"conntime" : 1434886856,
"version" : 70001,
"subver" : "/Satoshi:0.8.99.15/",
"inbound" : false,
"startingheight" : 484092,
"banscore" : 0
}
]
gjh@chrome:~$ ifconfig
eth0 Link encap:Ethernet HWaddr c8:60:00:be:3f:f7
inet addr:5.9.56.229 Bcast:5.9.56.255 Mask:255.255.255.224
inet6 addr: fe80::ca60:ff:febe:3ff7/64 Scope:Link
inet6 addr: 2a01:4f8:161:52e1::2/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:209313064 errors:0 dropped:514695 overruns:0 frame:0
TX packets:278628915 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:119352316807 (119.3 GB) TX bytes:128921890770 (128.9 GB)
AIUI, Qubitcoin is still limping along. The blockchain remains active so I don't consider it “dead”. You haven't chosen to favour us with your definition of “dead” (I suspect largely due to you not having bothered* to put in the intellectual effort to build an understanding of what “dead” means for a p2p app) but it'll have to be a deeply idiosyncratic one because of all the facts you choose to ignore. At this point, if you were a friend of mine, I'd be advising you to concentrate on identifying some hard facts to counter your horribly flawed understanding. This is a topic concerning dead coins, I have an interest in characterising the definition of such. Any list is necessarily and inherently out of date as soon as it is published but you can try picking the bones out of this one: https://minkiz.co/coin/inactive/You are quite poorly informed and your risk model is totally off the wall as a consequence. You're positing the existence of a single bad actor with a ludicrous work rate when the evidence in the source code itself suggests only that a small cabal of serial altcoin devs might be responsible for somewhere around 50-60% of launched alts. A recent case in point: compare the source code of transformerscoin and dubstep, launched within a couple of weeks of each other. Of course, if you have any actual evidence for your particular notion, do trot it out. Cheers Graham * you can take it as a compliment that I consider you likely capable of such a task |
|
|
|
Even running version 0.30.16.8 in a new folder (without wallet.dat or blocks) it crashes on start-up.
Try with --litemode=1, cures the problem for me on Ubuntu 14.04 Cheers Graham |
|
|
|
My point is that I find it remarkable that when I post some facts about a developer that he clones many coins and uses many account names there is always some "plausible denial" from someone. If I want to find out from who, then there are always some connections from the poster and that developer.... Hmm, this has descended into trolling. 1. You posted unsupported allegations, not facts 2. “never substantiated” != "plausible denial” And your sceptical stance does not justify offensively gratuitous innuendo. Cheers Graham |
|
|
|
|
Show Posts
