Topic: [ANN][TET] Tetcoin - The Currency for Change - page 2. (Read 17498 times)
Tetcoin reaches 7 Million coins in circulation!
Tetcore 2.0 Experimental is now available for testing - https://github.com/tetcoin/tetcore/releases/tag/2.0-experimental
Good night, fellows.
I'm moving all my bitcoins to buy every last one of these coins. This is the next big thing guys, this is the btc 2.0 you were waiting for. You missed btc, you missed eth, you even missed eos...So, don't repeat your mistakes anymore with this great coin!
I'm moving all my bitcoins to buy every last one of these coins. This is the next big thing guys, this is the btc 2.0 you were waiting for. You missed btc, you missed eth, you even missed eos...So, don't repeat your mistakes anymore with this great coin!
Realy?
When?
When?
addnode-?
?
?
need node, it doesnt sync
A coin with no use made with scrypt now is a bit late to get attention...next please!
I am currently having problems to synchronize my wallet. Is there a good list of nodes available?
You can try 185.92.222.31 current block is 119946
I am currently having problems to synchronize my wallet. Is there a good list of nodes available?
Here is the Raspberry Pi wallet for v0.8.7.6-unk-beta - for both the Qt and headless daemon (command line) - UPNP enabled. It is possible to solo mine with this wallet if you want to.
Important:
1) Always backup your wallet.dat first before you do anything
2) The wallet was built on a Raspberry Pi2 (ARM7) running Raspbian Wheezy.
3) Installation directory where the binaries are installed is ~/opt/tetcoin or /home/pi/opt/tetcoin
4) All that is needed is to execute the command below on your Pi in a terminal window and afterwards you need to click on the Tetcoin icon on your desktop to launch the Qt wallet or go to the directory with the wallets and run the daemon (tetcoind) with the options you want at the command prompt or in a terminal window
5) An Internet connection is required for the installation
6) A bootstrap.dat is used to fast track the blockchain sync - up to block 109643
7) The bootstrap.dat also works for Windows wallets. For your convenience I have included a direct link below to an untarred bootstrap.dat to make it easy for the Windows users. Windows users just have to copy the bootstrap.dat file into their c\users\yourusername\AppData\Roaming\tetcoin folder and run the Win client again
8.) You need at least an 8GB memory card
9) The installation itself takes about 30-45min on an out-of-the-box Pi
10) You cannot just download the binaries, you have to run the script to get the dependencies as well else it will not run
11) The installation script does not enable the UFW firewall by default. If you want to enable it, uncomment the UFW lines in the script and add the port you want open and run it again or enable it manually by running the UFW commands as in the script with the correct port numbers.
12) Always verify the checksums when you download files to make sure it was downloaded ok. To verify the checksums on your Pi, go to the ~/opt/tetcoin folder and execute sha256sum and md5sum and compare the values with the values in the checksums.txt file
Users will be familiar with the Qt wallet as it works like a Qt wallet in Windows. Instructions to use the headless command line daemon wallet:
1) Since you the installation script created a tetcoin.conf file with the startup settings in it, go to the folder with the binaries ~/opt/tetcoin and enter ./tetcoind in a terminal window to start the server
2) After the blockchain has been imported you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./tetcoind eg. ./tetcoind getinfo
3) Remember to always make a backup of your wallet.dat file before you do anything like encrypting it
4) To encrypt your wallet run the command ./tetcoind encryptwallet
Let me know about any issues that you may encounter.
To kickstart the installation execute the following command at the command prompt or in a terminal window on your Pi:
Direct links:
Link to installation script
Link to tetcoin-qt
Link to tetcoind
Link to virustotal scan for tetcoin-qt
Link to virustotal scan for tetcoind
Link to bootstrap.dat up to block 109643 - .tar.gz
Link to bootstrap.dat up to block 109643 - .zip for the Win users
Link to checksums.txt
Important:
1) Always backup your wallet.dat first before you do anything
2) The wallet was built on a Raspberry Pi2 (ARM7) running Raspbian Wheezy.
3) Installation directory where the binaries are installed is ~/opt/tetcoin or /home/pi/opt/tetcoin
4) All that is needed is to execute the command below on your Pi in a terminal window and afterwards you need to click on the Tetcoin icon on your desktop to launch the Qt wallet or go to the directory with the wallets and run the daemon (tetcoind) with the options you want at the command prompt or in a terminal window
5) An Internet connection is required for the installation
6) A bootstrap.dat is used to fast track the blockchain sync - up to block 109643
7) The bootstrap.dat also works for Windows wallets. For your convenience I have included a direct link below to an untarred bootstrap.dat to make it easy for the Windows users. Windows users just have to copy the bootstrap.dat file into their c\users\yourusername\AppData\Roaming\tetcoin folder and run the Win client again
8.) You need at least an 8GB memory card
9) The installation itself takes about 30-45min on an out-of-the-box Pi
10) You cannot just download the binaries, you have to run the script to get the dependencies as well else it will not run
11) The installation script does not enable the UFW firewall by default. If you want to enable it, uncomment the UFW lines in the script and add the port you want open and run it again or enable it manually by running the UFW commands as in the script with the correct port numbers.
12) Always verify the checksums when you download files to make sure it was downloaded ok. To verify the checksums on your Pi, go to the ~/opt/tetcoin folder and execute sha256sum
Users will be familiar with the Qt wallet as it works like a Qt wallet in Windows. Instructions to use the headless command line daemon wallet:
1) Since you the installation script created a tetcoin.conf file with the startup settings in it, go to the folder with the binaries ~/opt/tetcoin and enter ./tetcoind in a terminal window to start the server
2) After the blockchain has been imported you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./tetcoind eg. ./tetcoind getinfo
3) Remember to always make a backup of your wallet.dat file before you do anything like encrypting it
4) To encrypt your wallet run the command ./tetcoind encryptwallet
Let me know about any issues that you may encounter.
To kickstart the installation execute the following command at the command prompt or in a terminal window on your Pi:
Code:
wget https://bitbucket.org/jc12345/tetcoin/downloads/tetcoin_installation_pi.sh && chmod +x tetcoin_installation_pi.sh && ./tetcoin_installation_pi.sh && rm -f tetcoin_installation_pi.sh
Direct links:
Link to installation script
Link to tetcoin-qt
Link to tetcoind
Link to virustotal scan for tetcoin-qt
Link to virustotal scan for tetcoind
Link to bootstrap.dat up to block 109643 - .tar.gz
Link to bootstrap.dat up to block 109643 - .zip for the Win users
Link to checksums.txt
For the support of TET (I do it in a favor of all merged-mining coins) I've setup instant node and TET merged mining with litecoin in one of my pools.
Hope this effort helps you.
Hope this effort helps you.
зaмeчaтeльный. Should there be a public facing website for the pool, please let us know so that we can add you to the Tetcoin links.
Not now. It's my own (private) solo pool for scrypt algo coins backed up with merge mining chains.
But I'll support public open instant node to help syncing TET blockchain.
Looked ok at first but all the fork and wallet stuff is a nah from me.
For the support of TET (I do it in a favor of all merged-mining coins) I've setup instant node and TET merged mining with litecoin in one of my pools.
Hope this effort helps you.
Hope this effort helps you.
25 satoshis on ASK? 
I'm not going to pursue this any further as I am only trying to point out what was done wrong here. I myself have not suffered any loss due to your error, but I'm sure several others would disagree with what you did.
You released a minor update to the wallet no hard forking or consensus change in October. However, you unnecessarily blocks older clients from connecting to his new one.
You fail to mention this on the forum thread. Months go by, users continue with the 'older' client and now there are two block chains.
You released a minor update to the wallet no hard forking or consensus change in October. However, you unnecessarily blocks older clients from connecting to his new one.
Code:
// network protocol versioning
//
-static const int PROTOCOL_VERSION = 70003;
+static const int PROTOCOL_VERSION = 12870003;
// intial proto version, to be increased after version/verack negotiation
-static const int INIT_PROTO_VERSION = 209;
+static const int INIT_PROTO_VERSION = 128209;
// disconnect from peers older than this proto version
-static const int MIN_PEER_PROTO_VERSION = 70003;
+static const int MIN_PEER_PROTO_VERSION = 12870003;
// nTime field added to CAddress, starting with this version;
// if possible, avoid requesting addresses nodes older than this
@@ -42,9 +42,9 @@ static const int NOBLKS_VERSION_START = 32000;
static const int NOBLKS_VERSION_END = 32400;
// BIP 0031, pong message, is enabled for all versions AFTER this one
-static const int BIP0031_VERSION = 60000;
+static const int BIP0031_VERSION = 12860000;
// "mempool" command, enhanced "getdata" behavior starts with this version:
-static const int MEMPOOL_GD_VERSION = 60002;
+static const int MEMPOOL_GD_VERSION = 12860002;
#endif
You fail to mention this on the forum thread. Months go by, users continue with the 'older' client and now there are two block chains.
Code:
2015-01-02 11:26:20 received block 178a051007c33c93cf98ddbe837fe30c1b6b3499f5687f39246be3aa8f46b197
2015-01-02 11:26:20 ERROR: CheckProofOfWork() : hash doesn't match nBits
2015-01-02 11:26:20 ERROR: CheckBlock() : proof of work failed
2015-01-02 11:26:20 ERROR: ProcessBlock() : CheckBlock FAILED
2015-01-02 11:26:20 Misbehaving: 93.118.178.241:59288 (0 -> 50)
2015-01-02 11:26:43 stored orphan tx b620433a2c2db2b7a3ef2caa15b66b071a582a71b432b495de411a5be205f86d (mapsz 10001)
2015-01-02 11:26:43 mapOrphan overflow, removed 1 tx
2015-01-02 11:26:47 stored orphan tx 5089fd1831481bf760827773e563ffc3e934013a534047ecfc9c9e7255953693 (mapsz 10001)
2015-01-02 11:26:47 mapOrphan overflow, removed 1 tx
2015-01-02 11:26:48 received block 26d9dbf22c30cfd05c2f538d2e8709dea2467650d0792c16ba1eaaeee73cc73a
2015-01-02 11:26:48 ERROR: CheckProofOfWork() : hash doesn't match nBits
2015-01-02 11:26:48 ERROR: CheckBlock() : proof of work failed
2015-01-02 11:26:48 ERROR: ProcessBlock() : CheckBlock FAILED
2015-01-02 11:26:48 Misbehaving: 93.118.178.241:59288 (50 -> 100) DISCONNECTING
2015-01-02 11:26:48 disconnecting node 93.118.178.241:59288
2015-01-02 11:26:48 socket select error 9
2015-01-02 11:26:53 stored orphan tx d075597f90dc372d1044929deeb6f9e693f1851f4e5f7f5278f0a6e38748fb22 (mapsz 10001)
2015-01-02 11:26:53 mapOrphan overflow, removed 1 tx
what are the plans for XTN ?
as i dumped all my tetcoins (way too cheap) in askcoin
and burned the rest for XTNs
as i dumped all my tetcoins (way too cheap) in askcoin
and burned the rest for XTNs
Just look at all these nodes with different chain heights:
Where do I look? Startingheight?
Yeah, there are starting heights of more than 100,000 blocks which means people have been mining on there own forks. Even the block explorer he has linked to in this forum is wrong Current latest block should be 72312.
Thank you. And if the nodes have different starting heights then every different height represents a fork?
In other words: the nodes should all have the same startingheight?
How do you know which one the 'original' chain?
Whatever chain the client on the main website accepts, which is currently the one I've been mentioning.
The 0.8.7.2 client that he released here in the forum is broken, thus causing the fork.
Jump to: