Since I0Coin supports multi-sig addresses, it looks like it maybe should be able to be supported by the "distributed exchange" system found at
https://github.com/pharesim/HZx
I am not sure whether non-main nodes of the thing just run scripts directly under PHP or require setting up a web-server for the PHP to run under, the idea of having to run a web-server kind of put me of from just setting the thing up and giving it a whirl.
-MarkM-
Topic: [I0C] I0coin - The Best Choice In Digital Currency - page 52. (Read 82343 times)
Hi domob,
I was unable to run the 0.8.6-2 daemon binary on 64bit Xubuntu - error referred to db incompatibility, I'm using 4,8
I then compiled from master without error but got this error on startup:
Debug log:
Looks like it's trying to connect to btc ports despite me having the i0coin ports in the conf file?
Edit: Ah, wait. I just noticed that it's trying to use a bitcoin.conf file - I'll try again using the --conf option.......
I was unable to run the 0.8.6-2 daemon binary on 64bit Xubuntu - error referred to db incompatibility, I'm using 4,8
I then compiled from master without error but got this error on startup:
Code:
Error: Unable to start HTTP server. See debug log for details.
i0coind: /usr/include/boost/thread/pthread/mutex.hpp:108: boost::mutex::~mutex(): Assertion `!posix::pthread_mutex_destroy(&m)' failed.
Aborted (core dumped)
Debug log:
Code:
2015-09-15 12:44:10 Bitcoin version v0.11.99.0-9b336b2 (2015-09-07 16:42:14 +0200)
2015-09-15 12:44:10 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014
2015-09-15 12:44:10 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2015-09-15 12:44:10 Default data directory /home/rig/.bitcoin
2015-09-15 12:44:10 Using data directory /250GB/walletdata/.i0coin
2015-09-15 12:44:10 Using config file /250GB/walletdata/.i0coin/bitcoin.conf
2015-09-15 12:44:10 Using at most 125 connections (1024 file descriptors available)
2015-09-15 12:44:10 Using 4 threads for script verification
2015-09-15 12:44:10 scheduler thread start
2015-09-15 12:44:10 Binding RPC on address ::1 port 8332 failed.
2015-09-15 12:44:10 Binding RPC on address 127.0.0.1 port 8332 failed.
2015-09-15 12:44:10 Unable to bind any endpoint for RPC server
2015-09-15 12:44:10 Error: Unable to start HTTP server. See debug log for details.
2015-09-15 12:44:10 Shutdown: In progress...
2015-09-15 12:44:10 StopNode()
2015-09-15 12:44:10 Shutdown: done
Looks like it's trying to connect to btc ports despite me having the i0coin ports in the conf file?
Edit: Ah, wait. I just noticed that it's trying to use a bitcoin.conf file - I'll try again using the --conf option.......
I've now been able to create a version of I0coin based on the latest Bitcoin sources that is able to fully sync the blockchain. It can be found here:
https://github.com/domob1812/i0coin/tree/master
It still needs more testing, though, and the UI also still shows "Bitcoin" instead of "I0coin" everywhere.
However, I found that we need a minor change to the old client as well before it can support "headers-first" syncing by the new client. The modified version is I0coin 0.8.6-2:
https://github.com/domob1812/i0coin/tree/old-client
If you can (particularly if you want to run nodes to support the network), please upgrade to this version. Once enough nodes are updated, new clients can be bootstrapped from them. If you do not want to compile from source, you can try these binaries I compiled on 64-bit Ubuntu:
http://extra.domob.eu/i0coin-0.8.6-2.tar.bz2
Note that I do not have experience in compiling binaries for other systems than my own, so I can not promise that they work. Compiling from source is the best way. I've signed the binaries as well as the Git tag "i0coin-0.8.6-2" in my repository with my GPG key (see signature).
https://github.com/domob1812/i0coin/tree/master
It still needs more testing, though, and the UI also still shows "Bitcoin" instead of "I0coin" everywhere.
However, I found that we need a minor change to the old client as well before it can support "headers-first" syncing by the new client. The modified version is I0coin 0.8.6-2:
https://github.com/domob1812/i0coin/tree/old-client
If you can (particularly if you want to run nodes to support the network), please upgrade to this version. Once enough nodes are updated, new clients can be bootstrapped from them. If you do not want to compile from source, you can try these binaries I compiled on 64-bit Ubuntu:
http://extra.domob.eu/i0coin-0.8.6-2.tar.bz2
Note that I do not have experience in compiling binaries for other systems than my own, so I can not promise that they work. Compiling from source is the best way. I've signed the binaries as well as the Git tag "i0coin-0.8.6-2" in my repository with my GPG key (see signature).
We need DNS seed nodes.
If there is anyone who would like to be a seed node for i0coin please let me know. Post your IP here or PM me. We need a few seed nodes so we don't have to depend on addnodes in the config file so much. All I ask is that you be willing to keep your node active for a year or more since your IP will be hard coded into the i0coin client.
Let me add to this from the developer perspective: There are actually two kinds of "seed nodes" that can be hardcoded in the code. One is fixed IP addresses of stable nodes, which is reflected in the post above. You can also run the node behind a Tor hidden service (.onion address) if you want, and I can hardcode these as well if you post their onion address. These can be run behind a firewall and with a dynamic IP, and they help specifically users that proxy their I0coin connection through Tor.
The other is DNS seeds, which are set up by running a special script on a server (not an ordinary node). They monitor the network and dynamically keep a list of current peers. They are identified by a domain name (like i0coin.seed.mydomain.net) and those can also be hardcoded. This is the primary mechanism for node discovery in Bitcoin. If you are interested in setting up one of these, this would also be great. Let me know your domain name and I can add the seed to the code as well.
We're making progress with one person offering to setup a DNS seed node, and someone else offering a couple of stable addnode IP's. One thing no one has offered yet is to run an i0coin client as a Tor hidden service. This will allow Tor users to be seeded quickly. Is any one interested?
I can confirm that I'm working on upgrading I0coin to the latest Bitcoin upstream code. I've not yet created the Github repository for that, but my username there is domob1812, so it will probably be https://github.com/domob1812/i0coin.
Looking good domob - great work
Will this be a straight forward wallet update or will we be forking?........
domob hasn't mentioned any need for a hard fork. He's talked about a "soft fork" for BIP34 / BIP66 which would only kick in after 95% of the hash power is on the new client. So it should be pretty much a non-event as far as forking goes.
Exactly. There definitely won't be a hard fork. Also the "old" soft forks of Bitcoin (BIP16 and BIP30) are, seemingly, already done in I0coin. So there will only be forks for BIP34 and BIP66, but they are deployed with the new mechanism of Bitcoin which automatically kicks in based on miner support. Thus, they are mostly safe and do not require a fixed upgrade time.
I can confirm that I'm working on upgrading I0coin to the latest Bitcoin upstream code. I've not yet created the Github repository for that, but my username there is domob1812, so it will probably be https://github.com/domob1812/i0coin.
Looking good domob - great work
Will this be a straight forward wallet update or will we be forking?........
domob hasn't mentioned any need for a hard fork. He's talked about a "soft fork" for BIP34 / BIP66 which would only kick in after 95% of the hash power is on the new client. So it should be pretty much a non-event as far as forking goes.
From what domob tells me, he's working off a port from the latest Bitcoin github. So we're talking version 0.12.0, which hasn't been released yet for Bitcoin. The current plan is to release an i0coin client with the most recent 0.12.0 updates, then follow up with the full 0.12.0 release after Bitcoin finishes theirs.
I can confirm that I'm working on upgrading I0coin to the latest Bitcoin upstream code. I've not yet created the Github repository for that, but my username there is domob1812, so it will probably be https://github.com/domob1812/i0coin.
Looking good domob - great work
Will this be a straight forward wallet update or will we be forking?........
awesome
i've been waiting for a wallet update
We need DNS seed nodes.
If there is anyone who would like to be a seed node for i0coin please let me know. Post your IP here or PM me. We need a few seed nodes so we don't have to depend on addnodes in the config file so much. All I ask is that you be willing to keep your node active for a year or more since your IP will be hard coded into the i0coin client.
Let me add to this from the developer perspective: There are actually two kinds of "seed nodes" that can be hardcoded in the code. One is fixed IP addresses of stable nodes, which is reflected in the post above. You can also run the node behind a Tor hidden service (.onion address) if you want, and I can hardcode these as well if you post their onion address. These can be run behind a firewall and with a dynamic IP, and they help specifically users that proxy their I0coin connection through Tor.
The other is DNS seeds, which are set up by running a special script on a server (not an ordinary node). They monitor the network and dynamically keep a list of current peers. They are identified by a domain name (like i0coin.seed.mydomain.net) and those can also be hardcoded. This is the primary mechanism for node discovery in Bitcoin. If you are interested in setting up one of these, this would also be great. Let me know your domain name and I can add the seed to the code as well.
I can confirm that I'm working on upgrading I0coin to the latest Bitcoin upstream code. I've not yet created the Github repository for that, but my username there is domob1812, so it will probably be https://github.com/domob1812/i0coin.
We need DNS seed nodes.
If there is anyone who would like to be a seed node for i0coin please let me know. Post your IP here or PM me. We need a few seed nodes so we don't have to depend on addnodes in the config file so much. All I ask is that you be willing to keep your node active for a year or more since your IP will be hard coded into the i0coin client.
25,000 I0C Client Upgrade Bounty
20,000 I0C brooksby
5,000 I0C tinderbox
-----------
25,000 I0C Total Bounty
We need to move forward on the next version of the i0coin client. It will bring added security and more potential for developing the i0coin economy. The following criteria need to be met to claim the bounty.
1. Update must bring client up to Bitcoin version 0.10.0 (or later)
2. Maintain block retarget = 120 blocks (3 hours)
3. Merge mining must be operational
4. At least one major merge mining pool must start using client (to prove it works)
5. Maintain the memory streamlining features of i0coin version 0.8.x to keep memory usage to a minimum
(memory issue info here https://bitcointalksearch.org/topic/m.2830598)
Good news! We've got a taker on the bounty to update the i0coin client. I've asked him to post on this thread shortly.
I changed 1 and 2 on the bounty criteria. I bumped the minimum version up to 0.10.0, and removed the OP_RETURN byte size change. We'll leave it the same a Bitcoin.
25,000 I0C Client Upgrade Bounty
20,000 I0C brooksby
5,000 I0C tinderbox
-----------
25,000 I0C Total Bounty
We need to move forward on the next version of the i0coin client. It will bring added security and more potential for developing the i0coin economy. The following criteria need to be met to claim the bounty.
1. Update must bring client up to Bitcoin version 0.10.0 (or later)
2. Maintain block retarget = 120 blocks (3 hours)
3. Merge mining must be operational
4. At least one major merge mining pool must start using client (to prove it works)
5. Maintain the memory streamlining features of i0coin version 0.8.x to keep memory usage to a minimum
(memory issue info here https://bitcointalksearch.org/topic/m.2830598)
Remember to withdraw your I0Cs at Vircurex before end of the month folks. Just take big chunk of I0Cs to my wallet. Someones dumping their coins, other thanks for the cheap coins
we came in 2nd place
better luck next week
@brooksby
I'll contribute 5,000 I0C to the upgrade bounty.
We need a new exchange soon. Vircurex is delisting i0coin next month.
Yep, but that is also means that buy orders will be filled. Some people think if there is no exchange the coin is dead, which is not actually true
i0coin still has plenty of life. We just need some community help to get on more exchanges.
If you can spare some time please contact some exchanges to get i0coin added. If you need help with votes, post it on this thread.
Jump to: