let us spend out money mining cryptocurrency however we want.
It's speculation rather than investment and according to El Reg, it's now called “ funbux”. Just to bring a different perspective, I'm given to understand that the UK collectively spends £4bn a year on online gambling. Cheers Graham |
|
|
|
Compile issue:
wallet/wallet.cpp:4347:33: error: ‘class CClientUIInterface’ has no member named ‘ThreadSafeAskFee’; did you mean ‘ThreadSafeQuestion’?
if (fAskFee && !uiInterface.ThreadSafeAskFee(nFeeRequired))
^~~~~~~~~~~~~~~~
ThreadSafeQuestion
Not for the current codebase, it's commented out - https://github.com/gjhiggins/datacoin-core/blob/master/src/wallet/wallet.cpp#L4351. Please ensure you are using the current codebase. Cheers Graham |
|
|
|
Also, I've never seen this error message before when trying to load any sort of website. Care to explain what it means? I'm genuinely curious.
I'm not a webdev either. Your question would be better posed of the site operators, whoever they are. Cheers Graham |
|
|
|
Is this real life?
Not quite. This is work in progress that I published, an adaptation of Ahmad Kazi's work ( Primecoin intermediary and Primecoin Core). The (Datacoin adaptation of the Primecoin) intermediary client ( "intermediary" branch) functions as expected. The Primecoin Core 0.16 adaptation ( master branch) is not as straightforward. Thus far, I've managed to get it to sync up to block 4000-odd before it chokes, probably on an improper diff calculation or retargeting mismatch or some such gotcha. Running it under the debugger should throw a bit more light on the issue. However, the challenging task is to migrate the RPC getdata and senddata commands. 0.16 is a very different environment from 0.8, the architecture is quite different, much more complex and forces the simplistic senddata interface to make some heroic assumptions - about which wallet to use, about which account to use - about which txin to use to pay the fee. The API call itself basically fails to provide basic information for the construction of a transaction to store the data. I mean, I don't know whether it will fit ... do you have to send coins to send data also or can you just send data? who has sent some files with this already?
senddata is a lot like sendtoaddress. It creates a tx that contains: - data  - fee for this data - inputs (in order to pay fee) - output (for change) So the answer is: no, you don't need to send coins to somebody to send data. You can just send data. Sending a message means that there is a receiver for this message. senddata RPC doesn't add a receiver into tx but as soon as any tx has a data field you can do this (=> needs a bit of coding but doesn't need a hardfork).
The reason I published the work in progress is so that anyone who wants to pick it up and run with it isn't waiting on me unnecessarily. But it's work in progress. I don't even know if it works yet, I've only just now got it to compile successfully with the refactored API calls, now to find out whether it'll work okay without a receiver (new Bitcoin code can be much more strict about such things). Cheers Graham |
|
|
|
as you said, that it should be possible to rebase it on new v0.6 peercoin's base or not?
Not. Because of the havoc that PoS 2.0 and coin control will wreak on the ( carefully-constructed) existing model. It would be precipitate to implement profound changes to the emissions ratio without a detailed technical analysis and a fresh round of modelling. Cheers Graham |
|
|
|
I think such "hard fork", should be proposed, and voted
I strongly recommend that you first contemplate the remuneration likely required by someone fluent in C++ and with extensive experience of the re-development of elderly Bitcoin clones. Cheers Graham |
|
|
|
Having trouble getting any connections for clam. Does anyone have a list of nodes?
Happy to help ... addnode=185.52.2.48:31174
addnode=145.239.28.208:31174
addnode=118.102.74.85:34636
addnode=118.102.74.85:35500
addnode=5.9.31.67:38344
addnode=95.183.48.117:31174
addnode=178.63.60.7:54776
addnode=5.254.66.101:38398
addnode=178.62.8.78:31174
addnode=134.3.4.174:37628
addnode=170.130.28.170:43020
addnode=63.141.254.186:44907
addnode=159.203.5.220:31174
addnode=137.189.91.64:35917
addnode=132.148.153.239:46512
addnode=188.40.131.43:39950
addnode=104.239.139.17:31174
addnode=165.227.93.150:31174
addnode=46.4.113.143:31174
addnode=74.82.244.170:31174
addnode=158.69.32.10:47962
addnode=51.15.199.159:35640
addnode=69.121.201.75:55119
addnode=99.99.253.228:14841
addnode=219.136.252.124:58231
addnode=99.189.170.199:61944
addnode=193.70.47.2:51010
addnode=86.16.8.251:2225
addnode=76.90.200.205:37738
addnode=70.67.204.228:31174
addnode=46.101.33.61:58668
addnode=125.236.160.208:64639
addnode=158.129.212.236:31174
addnode=81.242.43.252:31174
addnode=37.189.255.136:52129
addnode=74.103.221.120:53871
addnode=47.145.211.77:63646
addnode=91.194.90.80:38148
addnode=5.196.57.80:47980
addnode=86.61.18.209:31174
addnode=212.92.123.182:42591
addnode=95.87.207.152:54982
addnode=78.46.108.202:31174
addnode=82.21.202.185:49677
addnode=67.205.153.62:58428
addnode=73.95.169.154:57155
addnode=99.250.80.197:62607
addnode=193.187.56.43:31174
addnode=219.136.252.124:57826
addnode=124.191.213.71:64795
addnode=194.166.221.237:64849
addnode=80.110.117.79:17909
addnode=109.233.58.44:51032
addnode=219.136.252.124:55692
addnode=219.136.252.124:63318
addnode=46.164.236.173:64269
addnode=79.8.1.204:62528
addnode=195.200.244.73:54136
addnode=73.170.212.102:49209
addnode=34.227.77.6:62841
addnode=79.231.182.70:54847
addnode=74.105.153.132:53581
addnode=104.237.4.26:34181
addnode=91.60.182.130:51130
addnode=24.122.244.181:31174
addnode=73.95.137.105:58922
addnode=173.230.186.109:50332
addnode=24.226.138.169:55099
addnode=23.92.221.66:47799
addnode=110.174.19.72:49431
addnode=180.245.107.23:55428
addnode=71.87.105.203:57686
addnode=109.153.80.107:50740
addnode=149.5.35.1:43528
addnode=166.70.203.230:11677
addnode=193.70.30.123:57800
addnode=178.221.133.40:55765
Cheers Graham |
|
|
|
We've dedicated two rigs to keeping the Datacoin testnet going.
That's welcome news for the group, I reckon. The following nodes have been seen active on the Datacoin Testnet in the last 14 dayz:
144.76.64.49:4776
64.130.139.90:4776
192.175.69.10:4776
119.9.108.125:4776
[2a01:4f8:13b:30a2::2]:4776
144.76.64.49:4776 is minkiz.co, which is currently hard-coded into the client as a dnsseed: https://github.com/datacoinproject/datacoin/blob/master/src/net.cpp#L1195 - (the Minkiz site is a long-term art project of ours, so I can be relatively confident that the service will persist for a few years more at least). Which of the above IP addresses are referencing your nodes? Cheers Graham |
|
|
|
“Thought leader”, maybe. But not “leader” in any sense that implies coercive power (i.e. “as we know it, Jim”) because in a network of pseudonymous peers, neither sanction nor coercion is available so there are no levers of power, only peers to be persuaded. If anyone's interested in building a deeper understanding: Frederick Laloux' Teal organisational model (informed by Ken Wilber's 60's model of human organisational development) would seem to be the closest-matching description. The implications of peer-to-peer networked cryptocurrencies being pure Teal organisations are quite intriguing¹. More usefully, the results of Laloux' work are presented prescriptively. Cheers Graham ¹ https://minkiz.co/library/a-different-perspective-on-cryptocurrency.html <- an introductory overview, which Ivory Tower denizens might find marginally useful. |
|
|
|
You tell me.
What would be a killer app for Datacoin?
IMO, Linked Data. It's where I'm headed, anyways. Cheers Graham |
|
|
|
Just for info ... Someone appears to be wasting CPU cycles according to this message, repeatedly appearing in minkiz' datacoin debug.log:
accepted connection 140.186.194.162:53509
PROCESSMESSAGE: INVALID MESSAGESTART
disconnecting node 140.186.194.162:53509
The IP address appears in chainz' listing as a "/Satoshi:0.8.3/" client but I don't know which organisation it's associated with. Cheers Graham |
|
|
|
Bumping from close to 2 years ago. Came back to this PC with all the old wallets on it. Started this one and it looks to be live.
Anyone here doing anything with it? Or just keeping some nodes up and mining for the hell of it?
Yeah, keeping some nodes up and mining, that about nails it (though I might take a look at upgrading to Core 0.16). I was curious to find out if it would keep ticking if run on a minimal network, which it seems to be doing quite nicely. (I was also quietly entertained that the "roulette" in Roulettecoin refers to its hashing algo and not some nebulous association with gaming, as nearly everyone seemed to incorrectly assume). Cheers Graham |
|
|
|
Importing Key appears to work now, doesn't show all my bee2 coins but that could just be based on when you forked the chain.
It appears that staking is working
Thanks for the feedback. I snapshotted the ledger a while ago, I'll update it so that folks' current keys work. Staking calculations do indeed seem to be working and that bodes well. However, the test addresses hat I used in the previous exercise did mature and were showing huge staking weight but when I stopped the script that was calling generate 1 every few minutes, so did the block generation. I have no experience of how the PoW->PoS transition works so I'll just have to build a model by working through the code than implements it. The situation isn't helped by the fact that the transition was implemented in the old 0.8.X navcoin and the 0.13 Core version may not even include that code. Cheers Graham |
|
|
|
I hope that the community can all get ready to help test the next release on a certain date and time.
I wish it were as simple as that. I don't have the resources to create a model network to work with, so I cannot know whether PoS will work or not and so am hardly in a position to announce a test with all the false expectations that will inevitably arise. anyway, in the interim, I made a few changes in a separate branch, named "rewind". The ledger is now implemented as address-balance pairs: https://github.com/gjhiggins/been/blob/rewind/src/chainparams.cpp#L64 so now anyone can search for their Bee address in the list and check the balance. I re-cut the genesis block and reset the blockchain back to block 0. https://github.com/gjhiggins/been/tree/rewindThe API generate call is functional - blocks are generated on demand. Bee privkeys should import and the balance should correctly appear. (It won't confirm unless you hand-crank the blockchain with generate). Cheers Graham |
|
|
|
Bottom line is that the Datacoin developers are now hard at work on a Datacoin Core 0.16 client.
Whilst I I understand the enthusiasm, I prefer realism - “hard at work” is misleading. Cheers Graham |
|
|
|
Is there a newer wallet available? 0.9.0 is eating lots of memory. I see that there's Voroshi 0.9.2.2 on the explorer for some nodes but I can't find a compiled version. Thanks! where to get the purse version 0.9.2.2? I'll have a response mid-to-late next week. Cheers Graham (development has been extensive but something of a slow burn: https://github.com/gjhiggins/vcoincore/branches) Cheers Graham |
|
|
|
|
Show Posts
