Actually, what needs to be verified is if you have a wallet from the old client, will it work if you copy it to the new client?
Any specific thing you want me to look for, other than that the balance transfers? So far all my tests from 3.24->8.6->9.2 have confirmed that already. Was going to do one or two more small transaction tests, and report here only if I found a problem, so far none. If the new clients crashes using a block chain from an old client you can always just download the whole blockchain again, instead of reindexing. Then you don't need to use the FrictionlessCoin client. So it shouldn't be a show stopper.
Exactly. Interesting, my guess is that there is something different in the difficulty calculations in the ahmed_bodi executable.
Anyway, still waiting to see when the 9.2 executable gets into the ghash.io miners.... we only have about a month left to go.
Difficulty calcs, Hmmm interesting, there are still some coins based on that old database structure, nmc comes to mind, they will have to solve the problem or tell all to re-downloading the blockchain, it will be required. I'm actually kinda of excited about the likelihood of Ixcoin being merged mined on PolyMYR for awhile first. Ghash.io/Cex.io can wait until it's been tested thoroughly. as well as review the source and install whenever they have time. Right now I'm pissed at them, in less than 24hrs after deadsea33 had the blockchain webpage for Ixcoin statistics built, CEX.io upgraded their front page graphic and their programmer forget to include the IXC/BTC trades. So now you have to log in to view the price/volume info or use the public API, it works without logging in. @deadsea33 - so now when you click on the statistics button for that blockchain webpage, it brings up a blank graphic. Love the chain and start of your efforts there, looks really cooool! As soon as we can start fresh or gain control of the ixcoin github acct, I'd like to see the webpage development source checked in, where we can keep it maintained and work on it as a team. Daily update for everyone. Currently running the 0.9.2 Client myself. Synced up ahead of the block where merged-mining started I'll let it sync fully and then we can start up testnet and do some merged-mining on myriadcoin's PolyMYR pool. O nce thats done the network urgently needs some new DNS Seeds. Other coins have 15+ while we have 0. After that we can roll out the clients  EDIT: Also Reverted the switch to a 40 Byte OP_RETURN by the bitcoin dev's EDIT No 2: 1 hour and 30 Mins, 1 Blockchain Rescan Later. The client is fully synced. Time to get some Win QT's out Don't we need at least an 80 Byte OP_RETURN for counterparty? Thats what i've done The Bitcoin devs switched from a 80 to 40 Byte OP_RETURN so i switched it back to an 80 Byte OP_RETURN @all - Highlighted above the need for DNS seed nodes. @ahmed_bodi - So what's the word, any updates here on that progress?  Good Read from ahmed_bodi's post here: Re: Multi-vPoW - Myriadcoin's Solution to Parasitic Merge Mining: https://bitcointalk.org/index.php?topic=725991.msg8235818#msg8235818Starting in Sept, I'll try to be available allot of the time for support in the ##ixcoin channel on freenode, anyone having troubles with an upgrade can find some help there. @foundation - Are we going to have a wiki.ixcoin.<something> server/site? I'm asking because some documentation in the client console help text(coded) needs to be adjusted if we don't. 5BTC for hero accts, fck U CfA. Hope BCT reverts all account here to newbie status & zeros out your investment. For those that don't understand, Read Zerohedge's post by Cognitive Dissonance from Aug 17th Control the Language and You Control the Mindhttp://www.zerohedge.com/news/2014-08-17/control-language-and-you-control-mindGR |
|
|
|
|
Cryptsy suspend the account, someone(s) must be mining directly to the exchange & more than likely lurks here - STOP before your suspended.
@meeh & team - great job with all the updates and progress!
|
|
|
|
for those upgrading from an old wallet without level db support (before 8.x) I would just make a backup (always) of your wallet before trying 9.2
I have not had a chance to build it and try it yet , is on my list of things to do.....
Understand & thankyou, that is very short & simple advice for those upgrading the Ixcoin wallet. I've been testing the different ways today & will report more below. From what I can tell, the wallet.dat file can be copied into any of the different builds and works just fine. No coins have ever been lost by me, always backup. To the person asking for a button to return your coins to you after you hit the send button prior to a certain number of confirms , once the coins are actually 'sent' (nothing is actually sent other than information but we will stick with the analogy) it is a done deal. Period.
The entire code base of bitcoin is designed to prevent double spending !! (obviously iX and many other coins based on this too)
What you are asking for is contrary to the whole system.
That would be me, understand what your saying, was attempting to think out of the box, to that day in the near future, when Ixcoin no longer has any mined coins, only transaction fees. Pretty sure the premise I was attempting to make, is not contrary to the whole system, if I'm wrong please help me to understand. Imagine the transaction fee you offer while sending a payment is not excepted by any miner. What then? Your send will never get even 1 confirm. What does a noob have to do in order to deal with this in todays environment? I've a pretty good idea, but never actually had to contend with the problem, so yes I'm arguing that it is not a done deal when you click send, until a miner excepts it. There needs to be 'some' way out there for users to ascertain what fee will likely get a confirm, preferably before they click send, code needs to be in the client (somehow), either as a list before sending (based on current tx fees offered by a group of miners) or how else will anyone ever send anything when suddenly the Tx fee jumps to 0.1 IXC or more? A user is left with testing higher and higher fees, by manual trial and error, having long periods of waiting in between, and fixing files from backups...etc Too painful to ever use. It's not a double spend problem, its a try to spend once problem. Will do just that, thanks for the links cinnamon, I'm sure my understanding of those topics can & will be improved. Update on my testing, I'll try very hard to be brief... This is for coin holders still running Thomas's final client release back in '11...aka: ixcoin-0.3.24.3-win32 Today I got a clean download of the blockchain using that client, and transferred a small amount of coin into it, so it had one transaction. Backed everything up and proceeded to attempt various upgrades to it. To my dismay, both ahmed_bodi 9.2 & cinnamon_carter's 8 builds crashed after a short while, never in the same place & I've been looking at logs and tested it a couple of different ways, then decided it wasn't really that important, because when I tried FrictionlessCoin's executable, it worked flawlessly the first time and reindexed all the blocks from disk, right up until today with no problem. You are left with nearly a 1GB of 'junk' files from the 'old days', but it worked. Then I applied ahmed_bodi 9.2 executable to those files and it instantly popped up without any re-indexing on disk or any other download, the client was ready to go. Wallet has the small amount of coin in it, tomorrow I'll do some more testing with sending/receiving, but everything looks good to go, and there is an upgrade path for those of you that haven't checked in for 2 or 3 years. Credit to FrictionlessCoin for making this possible. GR |
|
|
|
Ixcoin network is really humming along today, although Ixcoin data files only takes ~600MB of diskspace, had to scramble to get more C: space, 90+% of the blockchain downloaded, using the old 3.x client. Might be able to give this double version upgrade in one jump, another try l8r.... @Vlad2Vlad - Ok understanding the history better, yet IMO what another man does with his private keys is not any of my business. They are Thomas's property to do with as he/she sees fit, if you have some kinda agreement, let us know publicly, when your able. @INSTANTpr - Interesting what your doing, my hope is we can keep deadsea33 focused on Ixcoin  . Also the (POD)eveloper folks have an interesting solution, it's becoming clear to me that its the miners whom are becoming the dev/coders of note in this industry, perhaps it's a natural coin evolution thingy.... Having foundation(s) and/or Proof Of sites which expose individual identity/liability as well as those offering resources in good faith, all sound like a win-win for new ideas to develop. Wish you the best! Few coins, other than Ixcoin, have the history to speak for themselves, with over 3 years of blockchain, Ixcoin is and always has been BitCoin w/only a small twist, so soon only transaction fees will be awarded & what do we see? Multiple miners stepping up to the plate, what does that tell you? They must be sayin 'We'll take that money and move your blocks and hash that coin. As the fiat equivalent value skyrocket in bitcoin fees to send a transaction, we'll see an increase here too, maybe even a competitive state where Ixcoin transaction fees are quite volatile, my bet though is that we'll still be sending coins around, and for a fraction of the cost of a bitcoin fee. And Ixcoin's trade value? Pretty sure it will be a *wild ass* ride! Come join us! If anything additionally can be coded I would vote for this: A dynamic transaction fee calculation engine & user interface to support it: I'm not mining @ the moment, so don't lump me in that camp, yet I'm also not in favor of changing anything about the code for Ixcoin, other than what is required to be equal to Bitcoin. It follows in Thomas's footsteps philosophically . Easy upkeep. At least for right now. Lets get that right. The counterparty stuff looks interesting, yet if any additional code work should be done, it's to more easily cancel a coin send attempt. Those sends which fail, most likely will happen more frequently because the transaction fee(offered) is to low, no miner will process the block for me, those days are coming IMO, and we should put in better solutions for it, now if possible. So Help me out here, maybe this is already a non-issue and/or solved. Why is there no <cancel> button for a send? Making this 'Not so Scary' for new coin holders asking: What if my transaction doesn't go through? Will I loss my money? Seems having such a thing could help Ixc allot. So, how I understand this: The <cancel> button problem isn't really all that easy to solve, it would require at least *some* number of block times has elapsed, if no miner ever builds a block with that transaction in it (the one you want to cancel), it never leaves the wallet for the blockchain, only then could the wallet software return your funds and allow you try to send the transaction again, with a higher transaction fee & hopefully so that at least one miner agrees to except that payload price. Just an idea... GR |
|
|
|
Hmmm. I just did a fresh blockchain download which caused no issues for me. My guess is theres something different between the block databases or something
Ya that ixcoin-0.3.24.3 database structure is really old, I'm betting on it just because of my copy of the blockchain. I'll fire up the old client and do a fresh copy download here, then try to run the 9.2 executable on top of that and report back here tomorrow or the next day on how it goes.... |
|
|
|
@Vlad
Thomas will be back, based on his track record at the end of the month. I'm sure he will donate any funds.
@ all
I hereby throw my vote for Vlad to be ixcoin high protectorate. Don't let the trolls derail the conversation
Well, if you think he'll be here at the end of the month then I'm willing to wait until then before doing anything. Cause I'd rather have him on-board. And thanks for your vote - it is much appreciated. Edit: And thanks to Cinnamon as well for her vote of confidence. Actually I would rather not even have him 'onboard', Thomas obviously was done working on this long ago. Ahmed_bodi deserves the 50000+ bounty & if Thomas wants to be a benefactor or seller or whatever, I really don't care, IMO Ahmed_bodi, with a very minimal amount of work will be done with this upgrade & keeping it upgraded is highly likely. However the term' Lead Developer' covers more than just the code base, I understand that and see deadsea33's contribution to all of this as equally impressive. Many others too. Your efforts also really stand out Vlad, it would mean a greater share of your time, if you say: YES. I'll vote for you, if you want it, if not please step aside so the table is open. Thomas needs to turn over the keys to the code repository, as to the coins, I can not say, they are his to give or sell. Pretty simple really, GR |
|
|
|
@deadsea33 - Saw your foundation and coin webwork, really impressed....  For those wondering: Latest 9.2.1 source and win32 exe: Ahmed_bodi finally caused the app to crash. Thought I would try another test, upgrade the very old xcoin-0.3.24.3 blockchain to the new ixcoin-qt-0.9.2.1 based file system, started ok and I was going to post a positive, then just past block 96120 the app exited with only the Win message that it had terminated. Problem maybe because of my local files, could someone else test to see if you get a proper wallet & blockchain upgrade directly from 3.x to 9.x??, one that happens from a simple disk reindexing, no redownloading 3 years 14 weeks of blocks, its painful. Until this is resolved I would recommend that a IxCoin holder First) upgrade the wallet from 3.x to 8.x code, use Cinnamon_carter's latest build or FrictionlessCoin's release worked for me. Second) Install the new ixcoin-qt-0.9.2.1 executable, it will then again run a reindexing & bring the wallet and blockchain files to the 9.2 versions. Third) If you want to save some disk space, Delete the log files, they will be huge, also you have allot of old database structured files that are no longer needed, and can also be deleted. Here is the latest 8.x version: Glad to help out, and thanks so much for your work! |
|
|
|
@zebedee - perhaps you should go the cremation route. Thanks for this effort cinnamon_carter, really like having qr code support in a client. As your branch here is off the 0.8.6 code from frictionlesscoin & not the 9.2 code base Ahmed_Bodi has created, that source found here: https://github.com/IXCoin-Dev/IXCoinFelt it worth pointing out to folks, (aka deadsea33) jumping up and then back down a version while testing different 'ALPHA' client programs, your lucky if all you need to do is a blockchain rescan. Looked @ your code changes to fix those rpc commands, had not forgotten about that issue cinn, running 9.2 here & just executed the getblocktemplate/getwork commands in the v0.9.2.1-g752ecec-beta client console, they seemed to return good responses, without any errors or a client crash, other than that I've no idea if they are really working as you need, or what source code diff there is between them. The link to that Win executable is somewhere back in this thread...know he had some units of measurement source changes((mIxc & uIxc) since the last .exe compile, perhaps that fixed and a MAC version would be great, and then also just figured out we need to have an update on the Ixcoin 0.9.2.1 build date, it says July 4th, 2014. @cinnamon_carter - Was hoping you would look over how the merged mining code in v9.2 'feels' too you, and report back, no offense to Ahmed, the fact he intends on releasing it fully tested and ready to run MM on a major pool is outstanding. Yet IMO the more understanding eyeballs we get on that section the better for Ixc and many other alts, we need to be able to formulate a proof of the merged mining technique used, perhaps even to save us from the same fate as zebedee... Where I'm at, is the whole issue of building the Ixcoin executable from scratch, gotta figure that out & then study the critical components and code changes which make that work is going to take me months, call me slow....I'll get there. GR |
|
|
|
Since http://walletgenerator.net/ has not yet delivered a paper wallet for iXcoin, in the meantime I tested Devcoin paper Wallet. Basically you pay the fee to transfer your coins as usual. Once you redeem the papaer wallet using the secret key, the address of the paper wallet joins the other existing addresses in your wallet. It worked smoothly. Really appreciate hearing from you on the paper wallet studies, agree its important and wanted to let you know I've been following |
|
|
|
The way I see it, what happens to Ixcoin, is a time marker, one that will echo what can be expected to happen to Bitcoin many years from now when all those coins have been mined, and I'm old enough to know that its a pretty good chance I'll be dead by then, so what happens here with Ixcoin interests me very much.
You're mistaken. IxCoin has no transaction volume, so will wither on the vine. Bitcoin will be the world's financial network, and fees will be higher than the block reward in 10 years time when it drops to 3.125 BTC, never mind 100 years hence. We've no disagreement about there being a lack of transaction volume for IxCoin, in my case however, I see it as a great asset going forward. Talk about the car setting in the parking lot all gassed up & ready to go...Just *Look* at all that cheddar! How things really play out will likely be different than either one of us expects. Anyway my attitude is we'll seeGR |
|
|
|
|
Reminds me of a person(left) partially merged with a computer/network & about ready to arc weld another transaction into the blockchain(rightside), what better way to think of it.
Cool by me Vlad, didn't know the decision had been made & kinda liked that one anyway...
|
|
|
|
Been trying to get a few minutes in to post on here for days, keep getting interrupted. Blow me away, great job ahmed_bodi, the 9.2 client is so close to showme time I'm without words... Saw the units of measure coding correction you posted yesterday, uploaded to github before I even had found the problem. Also been reviewing sections of code & was trying to find a post from over a week ago, something about how we needed ixcoin nodes to code in for the release, anyway was stumbling over sections like this in chainparam.cpp: hashGenesisBlock = genesis.GetHash();
assert(hashGenesisBlock == uint256("0x0000000062558fec003bcbf29e915cddfc34fa257dc87573f28e4520d1c7c11e"));
assert(genesis.hashMerkleRoot == uint256("0xe61339a40aa4e90e983fe0d64cf09eed5fa1e6eac227b6761f06ac7af1929baf"));
vSeeds.push_back(CDNSSeedData("devtome.com", "dvcstable01.devtome.com"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable01.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable02.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable03.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable04.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable05.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable06.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.org", "dvcstable07.dvcnode.org"));
vSeeds.push_back(CDNSSeedData("dvcnode.com", "node01.dvcnode.com"));
vSeeds.push_back(CDNSSeedData("dvcnode.com", "node02.dvcnode.com"));
vSeeds.push_back(CDNSSeedData("dvcnode.com", "node03.dvcnode.com")); so was again wondering, about that question. Looks to me like we probably need to have something other than dvcnode.com/dycnode.org sites listed in our(your) future releases. Could the community here please give me some input about what should be coded? Other thoughts, ...kinda took my breath away when I saw that 3+ years of block chain needed to downloaded. loved that the new client comes up and asked where I want to store my data files, your 9.2 download seems to be working way beyond my expectations from a client perspective so far. NOTE: Perhaps someone here also knows how to create a bootstrap.dat file and upload the torrent, before I can figure it out....suggestion: It would be nice to have one made, just after the last block is mined... Love having a network traffic graph in the client... To bad the foundation people never finished making a decision on the logo....hint-hint Know allot of that is just because of the latest bitcoin core, yet felt it was worth making the point----> The 9.2 client appears to me that its almost ready to go!!!. @ahmed_bodi - If anything is wrong, I haven't seen it yet, will keep testing & reviewing the code. Any reports on how things are going from a merge-mining perspective, will be greatly appreciated. Going forward, looks like security will be on everyone's mind, more than ever. Some of you might have trouble syncing up on a clean install with the 9.2 client we're testing, I didn't, after 1-2mins it was going to town & had figured out some good peer connections. So I canceled that download, deleted my blocks & chainstate subfolders & copied over the 8.6 blockchain to the test dir, it then synced up instantly and was idling a couple hours before I did this console query, abrev & sorted peers list from the JSON output follows: Welcome to the IXCoin RPC console. getpeerinfo LIST "subver" : "/Satoshi:0.8.6/", "addr" : "92.97.27.98:8337", "addr" : "98.165.136.148:8337", "addr" : "167.160.36.73:8337", "addr" : "188.226.177.232:8337", LIST "subver" : "", "addr" : "62.210.198.84:8337", "addr" : "50.116.20.183:8337", "addr" : "50.46.245.151:8337", "addr" : "68.168.104.10:8337", My guess is a ixcoin.conf file with those first 4 added should do the trick for some of you, as they were listed as running subver 0.8.6 on my end, another idea is to try the console commands (haven't tested either yet myself), guessing it would look something like this: addnode=92.97.27.98:8337 addnode=98.165.136.148:8337 addnode=167.160.36.73:8337 addnode=188.226.177.232:8337 l8r... GR |
|
|
|
|
Looks like the trolls are starting to herd...
@Vlad - all sounds good, positive moves thankyou. Having an unmoderated thread here really sucks, but wanted to add, like ahmed_bodi, had not really looked into why you want the counterparty stuff so badly, starting to see it as a good thing too, first allot has to get done & there is a long.... mile between here and released code imo. We'll get there.
GR
|
|
|
|
I agree it does. Where ive forked off of his commits look to have a lot of compiling issues. I plan on using his latest commit and work backwards removing devcoin's specialised code to make it into a blank template to make it easy to pull bitcoin's changes. and then build IXCoin from there.
Great to hear, Ya that sounds good & absolutely the shortest route to completion, yet having a longer term perspective on maintenance. |
|
|
|
If you want to take a crack at the 0.9.2 upgrade, then go ahead. If you got any questions, then don't hesitate to ask me. I did the port of the 0.8.6 version but really don't have the bandwidth to work on the 0.9.2 upgrade.
It however would be a good learning experience.
Agreed, thanks for your support! I am going to let it play. I want to see what happens when the coins are mined out.
Eventually I may update iX to 9.2 , now after more study I am pretty confident I can pull it off. Aux pow and all.
Since others involved with the coin mining seem to be in no hurry to state what their plans are or to bring out other updates that were to be complete a long time ago I am in no hurry to code updates or fix known issues in the present code.
I am not in this for the money or the coins, just the lulz.
Glad to hear it CC, really good to have you here with us. The Aux pow(aka MM aka Merged Mining) code concerns me greatly, but I'm confident we'll have the best and right stuff when its time to go live with a public 9.2 release...probably in part because of your contributions.
Announcement:
Due to the lack of funds and active programming skills I am announcing a hold on all iXcoin development. This way the community doesn't constantly ask and wait for something to happen when clearly, nothing has changed.
When we get the necessary funds I will personally hire a programmer who can and will devote his/her time and effort solely to iXcoin. Until then I'm sorry to say we will simply sit and wait. Well, that's all we've been doing for the past 4 months even though bounties were paid out.
Frictionless, if you could please return the bounty you collected, to whomever donated it, that would be much appreciated.
If anyone wishes to donate any iXcoin [or Bitcoin] to the development fund please use the address below. Thank you all for your understanding, patience and support.
Best Regards,
Vlad
iXcoin Donation Address: xmvs1S55N5v1TN6xxWtxC9HaQPieBpAsQv
Bitcoin Donation Address for iXcoin development fund: 14RKvAdQsdneAKZmkBAntoDhx7Rkx8Yewe
Well we must be at the bottom, anyway sounds like you've reached it Vlad...  Think I at least partially understand where your coming from, but canceling the bounties and your plans to hire a programmer seem really off base to me, from here. The software development of this upgrade *IS* happening synergistically, as it should. Not from the barrel of a hired gun. IMO(& that is really all it is) what is needed from non-core wallet development is help making the people connections to insure the new code gets fully tested (by multiple parties) and working correctly before release, getting that expedited would be a big help. Let the upgrade unfold as it should, focus the Ixcoin foundation efforts on maintaining a coherent thread on here(BcT) w/links to a website that looks nice, yet works well even for folks w/very old or simplistic browsers versions(BcT does). It takes to much time to find out what is current with IXC, there is old stuff, unfinished stuff, dead links and miles of pages to read through to figure out what is current and what is not. And an important point, you may not be aware of for the core dev team, FINISH that logo decision contest, so it can be integrated into the next release as the time allows, from a programmers standpoint, its really crappy to have that hanging when everything else is done..... Get that new IxCoin announcement thread started today, put a link to the new(for most people) v8.6 frictionlesscoin wallet, it's been available to download for months now, I see no reason not to promote it. Anyone have a problem with that? When we get the necessary funds I will personally hire a programmer
What is the amount that is needed for this? Anyone?
-we also should expect Thomas to check in at the end of the month as per his track record, & maybe we can get him to donate some to the community take over development funds.
And who all controls the donation addresses? (in case, heaven forbid, Vlad gets hit by bus)
as an aside, we've had 4 part time devs so far right? each doing an update, so it makes sense for someone new to carry the torch.
1&2 Thomas and Fred (prob more Fred then Thomas)
3 doublec
4 Friction
Would suggest not updating that list until we actually see some source code get published and a release is pending, from ahmed_bodi's most recent post I'm really becoming optimistic that you'll have at least one name to add to that list, perhaps myself and/or a few others would be better than just one person imo. Until I've actually done something, would prefer to not be on it. Can't speak for Cinnamon_carter or the few others here that also have shown an interest, there are the makings of a good dev team shaping up though, one to keep IXC updated for the long haul. I've begun (More like 3/4 coded) an update to the IXC Source based off sidhujang's BTC-MM 0.9.2 codebase. If i get it completed im going to aim to keep it up to date with BTC.
Yaaaaaaaaa! Was looking @ that myself 2 days ago, sidhujang is way ahead of anybody else from what I could tell in completing this task, nearly daily updates for the DVC team, was trying to figure out what had been done for the merged mining part, so was looking at the source code files & didn't see much, just the start of what needs to be done, agree with you that is absolutely the correct place to be looking for how this is going to work out though! DVC has some tough problems to overcome, usage and inflation. At least we won't have the inflation part anymore |
|
|
|
@JohnnyBTCSeed - thanks for that, seems spot on...
There are lots of devs here, including me.
I don't understand the purpose of this coin yet.
What is it?
To do the things which Bitcoin can NOT...Good one, I like that! Its part of the grand experiment, no doubt about it. Just ran the numbers, current block is 215866, hard coded last block is 227499, so 11633 blocks to go, before mining new coins ends (~558K coins), that would be ~1800hrs or 72 days from now, if the block time is 8.9 minutes(just a wild guess, I didn't look it up). Expect volatility, it can be a good thing, if you own a few of these increasingly rare gems. Ixc has inspired me to learn about how to build wallets from source & focused my goals on the issues involved in this upgrade. Anyone who can do that for the BitCoin Core 9.2.x has a shot at this, Ixcoin is 99+% the same code, we just have to be absolutely certain to get the merged mining code absolutely correct, if it was easy someone in the NMC, DVC or I0C community would have it already, as far as I can tell they don't. The way I see it, what happens to Ixcoin, is a time marker, one that will echo what can be expected to happen to Bitcoin many years from now when all those coins have been mined, and I'm old enough to know that its a pretty good chance I'll be dead by then, so what happens here with Ixcoin interests me very much. Only a small investor, that bounty would push my share in the coins up over 30x, although I'm aware that the likelihood of my achieving it's full reward, before someone else gets there is near zero, being part of a team on this project is not out of the question, so attempting to learn the basics about crypto building & coding conventions, I've multiple decades of hardware & C/C++ experience, yet rusty might be the best word to describe where I'm at, brushing up those skills now, to hopefully be useful on this project. GR |
|
|
|
That's not I0coin, it's I/O coin.  your absolutely right m00x!, had to learn about this new I/O coin, sorry to those that followed my previous post, and were misled. I almost bought some thinking it was I<zero>Coin. That is too dam close in spelling, see now its a completely different coin. To make matters worse, it appears to me they are both trading @ near the same price, if you compare the Vircurex price here: https://vircurex.com/welcome/index?alt=btc&base=i0c&locale=enHad checked the Cryptsy dashboard for announcements of new coins before making that previous post, just checked again and still see no announcement of this addition to their lineup, so thought it must be the old I<zero>Coin market, the only info they have right now on this new I/OCoin market description is the gethub source link....which is clearly a different coin. |
|
|
|
|
Well as I don't own any, so more than likely. Still coins like this can be very volatile, don't listen to my advice, do your research. Staying on topic here, it would seem to be fighting the monthly cyclic trend, plus it appears to be an experiment for Cryptsy, offering trade w/usd....
|
|
|
|
....but before the markets were dropping there was almost no volume on RDD (based on my Cryptsy observations last month or two)
it surprised me sort of that RDD actually went up a lot while all the others pretty much tanked hard.
But not really because i had seen that happen lots before going back last year..
Ya noticed RDD going up here too...haven't followed the coin until I noticed Cryptsy made it available in usd, was wondering why the hell they are putting that 20 satoshi coin on the banker money trades. So turned it on for viewing in my dashboard for btc<c trading too & started watching it, still haven't installed the wallet or bought any, but find what its doing right now very interesting, trading @37 right now. Thanks for pointing out the monthly cycle, I had not noticed that fact before, really only started following alts since last Dec, pretty convinced its true though. As to proof to those wondering if this is 'real', was thinking about how to verify that yesterday, thought it would be an interesting problem to solve...one would have to feed allot of the time/price data for allot of the different coins into an FFT transform, look at the output in the frequency domain, if its real, there should be a peak around the 30-31 day mark. Anybody setup to do that? |
|
|
|
|
Show Posts
