Topic: Ixcoin TODO - page 132. (Read 631750 times)
I reckon now that this is done here is the source so i can show progress:
Github Source: https://github.com/IXCoin-Dev/IXCoin
Windows QT: Compiling ATM
Github Source: https://github.com/IXCoin-Dev/IXCoin
Windows QT: Compiling ATM
Bravo Ahmed...bravo!
And a windows wallet which actually compiles: Now you're just showing off. Haha!
Thanks a lot man, you pulled off a miracle in a single week.
Much appreciated!
I reckon now that this is done here is the source so i can show progress:
Github Source: https://github.com/IXCoin-Dev/IXCoin
Windows QT: https://www.dropbox.com/s/743o27bf80g850o/ixcoin-qt-0.9.2.1-win32.zip
Github Source: https://github.com/IXCoin-Dev/IXCoin
Windows QT: https://www.dropbox.com/s/743o27bf80g850o/ixcoin-qt-0.9.2.1-win32.zip
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. Once 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
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. Once 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
I can run a client on testnet when you are ready to test.
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. Once 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
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. Once 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
After you test out the merge mining functionality, can you work with CEX.IO to get the 0.9.2 functionality into their pool?
This is the current biggest obstacle in getting any new functionality into IXC.
As an additional upside, CEX.IO may just hire you for your pool development experitise.
Thanks!
I certainly can do. However at this point in time im not 100% CEX.IO would be wanting to hire me for my pool expertise. especially since i'd be running a competing pool
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. Once 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
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. Once 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
After you test out the merge mining functionality, can you work with CEX.IO to get the 0.9.2 functionality into their pool?
This is the current biggest obstacle in getting any new functionality into IXC.
As an additional upside, CEX.IO may just hire you for your pool development experitise.
Thanks!
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. Once 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
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. Once 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
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. Once 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
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. Once 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?
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. Once 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
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. Once 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
Well, excellent that you got it working. The 0.9.2 code base is nicer than the previous because it uses the standard automake to drive its makefile. There is a couple of spots in the code base that have markers when a BIP was enabled, you may want to either permanently disable those BIP changes or set them sometime in the future.
That shouldnt make a difference really. The only important BIP's i know of are BIP16 and 30 of which both were enabled ages ago
Use then the block height used by the previous version.
Yep i already have
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. Once 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
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. Once 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
Well, excellent that you got it working. The 0.9.2 code base is nicer than the previous because it uses the standard automake to drive its makefile. There is a couple of spots in the code base that have markers when a BIP was enabled, you may want to either permanently disable those BIP changes or set them sometime in the future.
That shouldnt make a difference really. The only important BIP's i know of are BIP16 and 30 of which both were enabled ages ago
Use then the block height used by the previous version.
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. Once 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
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. Once 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
Well, excellent that you got it working. The 0.9.2 code base is nicer than the previous because it uses the standard automake to drive its makefile. There is a couple of spots in the code base that have markers when a BIP was enabled, you may want to either permanently disable those BIP changes or set them sometime in the future.
That shouldnt make a difference really. The only important BIP's i know of are BIP16 and 30 of which both were enabled ages ago
While I was browsing the Bitcoin Foundation website, I realised:
There are so many tasks and positions to cover in a well structured organisation.
Probably boring meetings and paperwork is not part of Friction's nature. He is a man of action, the one doing the job, "getting things done" as he said once.
If you look at BTCF only a few, and sometimes easy targets for criticism, are board members. All the others occupy different and maybe more enjoyable positions.
I wonder Friction, since you know yourself and your personal condition better then anyone else, how do you think you could be better used in IXC Community?
Is there any way you feel you could happily contribute to IXC growth without affecting you to the point to feel unduly used by this community?
I think it's a matter of balance. Maybe we expected too much of you.
It doesn't mean you cannot still contribute, according to your personal schedule, to the support of this project.
Best Regards
There are so many tasks and positions to cover in a well structured organisation.
Probably boring meetings and paperwork is not part of Friction's nature. He is a man of action, the one doing the job, "getting things done" as he said once.
If you look at BTCF only a few, and sometimes easy targets for criticism, are board members. All the others occupy different and maybe more enjoyable positions.
I wonder Friction, since you know yourself and your personal condition better then anyone else, how do you think you could be better used in IXC Community?
Is there any way you feel you could happily contribute to IXC growth without affecting you to the point to feel unduly used by this community?
I think it's a matter of balance. Maybe we expected too much of you.
It doesn't mean you cannot still contribute, according to your personal schedule, to the support of this project.
Best Regards
Vlad has no idea about how to develop anything. So let's be real, we've had a couple of guys previously who did make a lot of contributions. Dexter44 and Luke, they've both left but before they did, they complained a lot about Vlad's back seat driving.
I have come to a point where I have little or no interest in working with Vlad.
You are however right, I really have no time for the boring administrivia stuff.
I think stepping back right now and letting other developers take a crack at this is a good thing. I have done my part to keep this coin afloat when there was no developer and no website. I find it extremely distasteful to be criticized by someone who had never made a single real contribution to IXC.
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. Once 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
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. Once 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
Well, excellent that you got it working. The 0.9.2 code base is nicer than the previous because it uses the standard automake to drive its makefile. There is a couple of spots in the code base that have markers when a BIP was enabled, you may want to either permanently disable those BIP changes or set them sometime in the future.
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. Once 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
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. Once 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
This is amazing - after less than 1 week, this code update, which was much harder than the 8.6 update, is nearly complete and....and we have had 2 actual real status updates and not the usual, "it's gonna get when it gets done [even though it's been 5 months now] it's not an easy update and I'm really busy." Haha!
I'm [pleasantly] shocked and stunned. And no demand for an upfront payment either. lol.
Thank you Ahmed Bodi, this community owes you their gratitude and if ixCoin does go up like I expect then I will definitely [personally] pay you generously for any work we may need in the future.
Thomas Nasakioto: Please do not delay payment for this man's hard work for months on end. If it's too difficult for you to read this thread once per week please designate one or more people for full access to the bounty coins [and the .org website].
Thank you!
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. Once 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
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. Once 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
I hope not your whole portfolio 
No, I think IXC will go to $100+ by next year and I wouldn't wanna get left behind in case it keeps going past $10. $10 is simply my short term target and a price which would induce me to sell a good sized block of IXC.
To be exact, I have 77,777 IXC for sale there. I had 2 of those blocks for sale but I removed one after CEX signed on.
We do not need iXCoin.co. Friction can keep it as a memento.
We have a much much better site at iXCoin.eu and I have several iXCoin domains which are better than .io and I can just point them to the .eu site.
iXCoin.co isn't worth $50 let alone what he's asking so don't be foolish to pay him anything.
The best site is iXCoin.org and if Thomas doesn't get off his ass soon and start cooperating I'll get a court order and confiscate it from him given he paid for it with this community's money.
Your foundation doesn't even have a website.
Thomas is absent most of the time and hasn't updated his website in years.
Luke has decided to focus his talents elsewhere.
Without any real skills, you folks in the foundation are like a boat without a paddle. It doesn't help your case by insulting the only one developer of iXcoin that has given a damn about it.
Edit: In case anyone tries to dispute the above claim. My brother at the same time paid $3,300 for exactly 28,000 IXC. So in actuality, friction got closer to $7,000 in pay for a copy and paste job which took 5 months. That's our charity guy....haha!
Not my fault that you advised your brother to buy at the peak.
I think you need to get a clue about the real world. Software development is very expensive.
Furthermore, IXC has rarely been at 10 cents, also it took me many months to even collect on the bounties.
Even if I did the 0.9.2 port, I wouldn't expect a prompt payment.
All I can say about IXC is that it has the stingiest owners, these owners would rather see the coin go to zero than pay out any bounties. So I'm going to sit here and wait until you owners can't take the pain anymore and finally shell out to pay for some real development.
Now go shut up and sit in the corner.
Is this a smear campaign against my name? Message me your private information. I will sue, you bet.
This is going too far. Outright brazen and nothing but ungrateful. YOU did nothing for IXCoin.
Reminder: BCFrictionless is some other user who seems to relish impersonating FrictionlessCoin.
Somebody hacked my account, probably Vlad2Vlad the scammer. This is not me posting.
I am FrictionlessCoin, solracx, Carlos Perez from CodeAudit.com. I can post proof. You are going to far. You know that this is highly illegal to steal my account right?
Now go shut up and sit in the corner.
Is this a smear campaign against my name? Message me your private information. I will sue, you bet.
This is going too far. Outright brazen and nothing but ungrateful. YOU did nothing for IXCoin.
Reminder: BCFrictionless is some other user who seems to relish impersonating FrictionlessCoin.
Jump to: