Terracoin Wiki - User contributions [en]

MediaWiki:Tweeki-navbar-left

2019-02-21T00:57:41Z

SixOfFive:

About
*What is Terracoin
*Roadmap
*Specifications
*Features
*Whitepaper
*Glossary
*Buy
*Exchanges
*Links

Wallets
*Terracoin Core Wallet
*Upgrading the Core Wallet
*Paper Wallet
*MultiSig (Multisignature)

Masternodes
*Linux
*Raspberry Pi
*Windows

Governance
*Understanding the Governance and Budget System
*Using Decentralized Governance: Proposals; Voting; and Budgets
*Governance Tools & Pages

Developers Guide
*Understanding Sporks

MediaWiki:Tweeki-navbar-left

2019-02-21T00:57:30Z

SixOfFive:

Sentinel

2018-01-02T20:43:23Z

SixOfFive: Created page with "An all-powerful toolset for Terracoin Sentinel is an autonomous agent for persisting, processing and automating Terracoin 0.12.1.5 governance objects and tasks, and for expand..."

An all-powerful toolset for Terracoin
Sentinel is an autonomous agent for persisting, processing and automating Terracoin 0.12.1.5 governance objects and tasks, and for expanded functions in the upcoming Dash V13 release (Evolution). Sentinel is implemented as a Python application that binds to a local version 0.12.1.5 terracoind instance on each Terracoin 0.12.1.5 masternode.
Governance Object
A Governance Object (or "govObject") is a generic structure introduced in Terracoin 0.12.1.5 to allow for the creation of Budget Proposals, Triggers, and Watch Dogs.
Class inheritance has been utilized to extend this generic object into a "Proposal" object to supplant the current dash budget system.

Masternode Network

2018-01-02T20:40:51Z

SixOfFive: Created page with "In addition to traditional Auxiliary Proof of Work (PoW) rewards for mining Terracoin, users are also rewarded for running and maintaining special servers called masternodes...."

In addition to traditional Auxiliary Proof of Work (PoW) rewards for mining Terracoin, users are also rewarded for running and maintaining special servers called masternodes. Thanks to this innovative two tier network, Terracoin can offer innovative features in a trustless and decentralized way.
What is a Terracoin masternode?
Terracoin uses special servers called masternodes to power PrivateSend, InstantSend, and the governance and treasury system. Users are rewarded for running masternodes; 45% of the block reward is allocated to pay the masternode network.
Masternodes enable the following services:
InstantSend allows for near-instant transactions. Terracoin InstantSend transactions are fully confirmed within four seconds.
PrivateSend gives financial privacy by obscuring the source of funds on the blockchain.
Governance and Treasury allows stakeholders in Terracoin to determine the direction of the project and devotes 10% of the block reward to development of the project and ecosystem.
Terracoin will make using cryptocurrency as easy as using PayPal.
Masternode owners must have possession of 5000 TRC, which they prove by signing a message and broadcasting to the network. Those coins can be moved at any time, but moving them will cause the masternode to fall out of queue and stop earning rewards.
Masternode users also are given voting rights on proposals. Each masternode has one vote and this vote can be used on budget proposals or important decisions that affect Terracoin.
How much can you earn from hosting a Masternode?
Masternodes cost money and effort to host so they are paid a share of the block reward to incentivize them. With current masternode numbers and rewards masternodes earn approximately a 30% return on 5000 Terracoin for the year of 2017. There is also the possibility for masternodes to earn money from fees.

InstantSend

2018-01-02T20:37:58Z

SixOfFive: Created page with "InstantX is NOW InstantSend (Rebranded May 2016) This paper introduces a new concept called InstantSend (transaction locking and masternode consensus). This technology will al..."

InstantX is NOW InstantSend (Rebranded May 2016)
This paper introduces a new concept called InstantSend (transaction locking and masternode consensus). This technology will allow for cryptocurrencies such as Terracoin to compete with nearly instantaneous transaction systems such as credit cards for point-of-sale situations while not relying on a centralized authority. Widespread vendor acceptance of Terracoin and InstantSend could revolutionize cryptocurrency by shortening the delay in confirmation of transactions from as long as an hour (with Bitcoin) to as little as a few seconds.

PrivateSend

2018-01-02T20:35:19Z

SixOfFive: Created page with "PrivateSend Basics PrivateSend gives you true financial privacy by obscuring the origins of your funds. All the Terracoin in your wallet is comprised of different "inputs" whi..."

PrivateSend Basics
PrivateSend gives you true financial privacy by obscuring the origins of your funds. All the Terracoin in your wallet is comprised of different "inputs" which you can think of as separate, discrete coins. PrivateSend uses an innovative process to mix your inputs with the inputs of two other people, without having your coins ever leave your wallet. You retain control of your money at all times.
The PrivateSend process works like this:
PrivateSend begins by breaking your transaction inputs down into standard denominations. These denominations are 0.01 Terracoin, 0.1 TRC, 1 TRC and 10 TRC --sort of like the paper money you use every day.
Your wallet then sends requests to specially configured software nodes on the network, called "masternodes." These masternodes are informed then that you are interested in mixing a certain denomination. No identifiable information is sent to the masternodes, so they never know "who" you are.
When two other people send similar messages, indicating that they wish to mix the same denomination, a mixing session begins. The masternode mixes up the inputs and instructs all three users' wallets to pay the now-transformed input back to themselves. Your wallet pays that denomination directly to itself, but in a different address (called a change address).
In order to fully obscure your funds, your wallet must repeat this process a number of times with each denomination. Each time the process is completed, it's called a "round." Each round of PrivateSend makes it exponentially more difficult to determine where your funds originated.
This mixing process happens in the background without any intervention on your part. When you wish to make a transaction, your funds will already be anonymized. No additional waiting is required.
IMPORTANT: Your wallet only contains 1000 of these "change addresses." Every time a mixing event happens, one of your addresses is used up. Once enough of them are used, your wallet must create more addresses. It can only do this, however, if you have automatic backups enabled. Consequently, users who have backups disabled will also have PrivateSend disabled.
PrivateSend Code Review
Over the course of August and September 2014 the Dash network commissioned Kristov Atlas, author of Anonymous Bitcoin, to conduct a review of the PrivateSend code (then called DarkSend+). This review resulted in a visualization of PrivateSend, a formal report analysing the privacy mechanism, and a response from Dash founder and core developer Evan Duffield.
PrivateSend Technical Details
PrivateSend is a novel, decentralized mixer for creating an on-demand system of removing the history from coins on the network. This is mainly for fungablity, which is the attribute of money that allows any token to be exchanged with any other token, without having a difference in price in the form of a premium for tokens with less or no history. Without PrivateSend, tokens with less history would become increasingly valuable as the network grows, because of their lack of association with prior transactions. Without fungibility, there is a risk that certain tokens could be “red listed” and lose some or all of their value if at any point in the past they had been found to be used in illegal or questionable activities. Nobody wants to hold money that was involved in illegal activity, yet after the activities take place, tokens re-enter the supply and pass to new users who had no connection with the prior illegal acts. We remove this issue with the implementation of PrivateSend, which is included as part of the core protocol of the Terracoin network.
PrivateSend Status Codes
The system has various modes which allow servers to keep track of the current state of their mixing pool. These mixingpools are single use, allowing three people to use them at a time. Statuses are idle, queued, accepting_entries, finalizing_transaction, signing_transaction and transmitting transaction.
Users begin by connecting to a node, which is in the idle state. The masternode then moves the wstatus to “queued” and issues a message to the network, telling other users that’s it’s currently available for mixing. Users can utilize multiple servers at a time to mix, what is called multi-session mixing. This greatly speeds up the mixing process at the cost of creating more addresses and thus requiring more frequent wallet backups.
Privacy Through Ambiguity
Mixing is the process of joining multiple transactions together, from multiple users, where all unique information about the users is removed from the transaction. Users send tokens to themselves through the system, and at no time do these tokens ever leave the users’ wallet. masternode operators are therefore completely separate from the process of mixing. masternodes simply serve as a transit method for the storing and signing of transactions, allowing users a safe place to initiate the process in an anonymous way.
Privacy is achieved by using denominated amounts of 10, 1, 0.1 or 0.01. Each session initiated on a masternode only carries a single denomination, such as having 10x 10D inputs and 10x 10D outputs. Users then individually sign their inputs to the collective outputs, allowing the transaction to be valid once complete and broadcastable.
Fee Model Anonymity
In other implementations of mixing software, fees can be used to break the transactions apart and identify users on the networks. On the Terracoin Network this is avoided by allowing masternodes a special type of message which allows them to broadcast fee-less transactions. We use this technology to decouple the fees from the transactions, so that for every 10 transactions using the PrivateSend technology, there is only one fee transaction. This prevents a timing attack on the PrivateSend implementation.
Phases of PrivateSend
The process begins when a user denominates some funds to be used as a “cash account,” then they simply tell a random masternode they would like to mix a specific denomination such as 100D. The masternode has no information about the transaction at this point, since the denomination carries no information about which inputs the user would ultimately like to mix. The masternode receives the request and issues a message to the network saying that it is ready to mix that denomination and that there is a user waiting.
At this point if other users are wishing to mix inputs of that denomination, they can connect to the masternode that is hosting the other user’s transaction. When three users queue themselves on the same masternode, the next stage, “accepting_entries,” is initiated.
In this stage, all users send their inputs and outputs to the masternode, where they are collected and put into memory until all users have identified the full list of inputs/outputs they would like to mix. Once this is complete, the process moves onto the next stage, “finalize.” At this point, the masternode sends a message back to the users, showing the merged transaction they all jointly created. All inputs are from the user’s wallet and all outputs are sent back directly to the user’s wallet. The funds involved in this process never leave the user’s wallet at any time, allowing the masternode to be completely segregated from users’ funds. This is how the process of PrivateSend remains trustless and secure, without risking user’s funds or exposing masternodes to excessive legal risk. Once the finalized transaction is approved, the process moves onto the next phase, “signing.”
Users sign only the inputs for which they have keys, and the funds are then released to all outputs simultaneously. It’s worth noting that inputs and outputs are not directly tied to each other in this process, since inputs are in a separated list and only tied to each other. Outputs are also in a separated list, only tied to each other. This means, literally, that all users are paying all users in this process. The users are not only paying themselves, but everyone else. This means you can’t say input #4 went to output #14 (e.g. you can’t trace the input to the output, they are processed in concert).
When all inputs are signed to all outputs, the transaction suddenly becomes valid, and the masternode broadcasts using a special message called DSTX. The network keeps track of these messages, allowing masternodes to submit one PrivateSend transaction every N hours without paying fees.

Masternode Diagnostics

2017-11-16T15:13:08Z

SixOfFive:

This page is a work in progress. More details will appear as further issues are diagnosed.

So you followed a tutorial or a script, setup your masternode and boom! It doesn't work. Why?

Check your masternode outputs (in debug console with the Qt wallet you can issue a "masternode outputs"). If nothing comes back except a couple of {} brackets, then you don't have 5000 TRC in a single transaction into that wallet. It cannot be multiple transactions that equals 5000 TRC, it must be 1 transaction of exactly 5000 TRC+network fee. Even if you transferred more (such as 5000.00000001 TRC, that is not exactly 5000 TRC and it will not work).

If you have a value returned, then you need to check the output on the masternode network to see the status of that. Do a "masternode list full output" where output is your output that was listed above when you ran masternode outputs.

masternode list full c313907f484140b1c92fd438dd1263639a7b97f523dfd7370ffff54c9d4dc5aa

{
"c313907f484140b1c92fd438dd1263639a7b97f523dfd7370ffff54c9d4dc5aa-1": " ENABLED 70206 17eqUknFNbFSFcuqDS8XnX4xqt5n1x3UBm 1510674967 207656 1510668460 1116315 104.236.58.131:13333"
}

In order to verify that there is something at least listening to that port you can use putty or telnet in a linux shell. Your masternode list full contains the IP address of your masternode at the end of the line. You will want to use that in order to check on your masternode.

telnet 104.236.58.131 13333

Trying 104.236.58.131...

Connected to 104.236.58.131.

Escape character is '^]'.

If you get a response like above, then the daemon is listening on port 13333 for your masternode.

telnet 104.236.58.131 13333

Trying 104.236.58.131...

telnet: Unable to connect to remote host: Connection refused

If you get a response similar to above, or the connection is closed right away in putty, then your daemon is not running, or is firewalled and cannot accept incoming connections.

If you are able to connect to the daemon, then proceed with further diagnostics on this page. If you cannot connect to the daemon, then you need to determine why that is (firewall rules, daemon may have crashed, OOM condition due to low memory on the VPS, etc)

Login to the VPS, and run "./terracoin-cli mnsync status" if that comes back with "IsSynced": true, then issue a "./terracoin-cli masternode debug". If it does not come back with IsSynced true then you need to wait for the daemon on the VPS to finish sync'ing the masternode data.

==Missing Masternode Input==

If the "./terracoin-cli masternode debug" comes back with "Missing masternode input", then you need to check the ~/.terracoincore/terracoin.conf on your server. (You can usually run a "cat ~/.terracoincore/terracoin.conf" to check the contents of the file). Make sure that you have lines similar to:

masternode=1

masternodeprivkey=5JTGQYU94eTaasEbNDFPdZR3negetaVSSoLrM9Z2vjJnG9Y9KCT

masternodeprivkey would be what you got from "masternode genkey" when following the tutorial on setting the masternode up.
If you do not have those lines in the file, then that is your issue, and you would need to put the proper values in that file (using an editor such as nano or similar.)

==Transaction Too Large==

If you get a "Transaction too large" when sending yourself 5000 TRC, you have too many inputs for creating your 5000 TRC output. You will need to send smaller transactions first, before creating the 5000 TRC transaction. This commonly happens from mining as you collect a large amount of small transactions. Try sending yourself 2 transactions of 2500 TRC before doing a single transaction of 5000 TRC into another address. If you get the same message when trying to send yourself 2500 TRC, you may need to go to 5 transactions of 1000 TRC first and then 1 transaction of 5000 TRC.

Masternode Diagnostics

2017-11-14T19:29:34Z

SixOfFive:

Masternode Diagnostics

2017-11-14T16:50:00Z

SixOfFive: /* Missing Masternode Input */

This page is a work in progress. More details will appear as further issues are diagnosed.

So you followed a tutorial or a script, setup your masternode and boom! It doesn't work. Why?

Check your masternode outputs (in debug console with the Qt wallet you can issue a "masternode outputs"). If nothing comes back except a couple of {} brackets, then you don't have 5000 TRC in a single transaction into that wallet. It cannot be multiple transactions that equals 5000 TRC, it must be 1 transaction of exactly 5000 TRC+network fee. Even if you transferred more (such as 5000.00000001 TRC, that is not exactly 5000 TRC and it will not work).

If you have a value returned, then you need to check the output on the masternode network to see the status of that. Do a "masternode list full output" where output is your output that was listed above when you ran masternode outputs.

masternode list full c313907f484140b1c92fd438dd1263639a7b97f523dfd7370ffff54c9d4dc5aa
{
"c313907f484140b1c92fd438dd1263639a7b97f523dfd7370ffff54c9d4dc5aa-1": " ENABLED 70206 17eqUknFNbFSFcuqDS8XnX4xqt5n1x3UBm 1510674967 207656 1510668460 1116315 104.236.58.131:13333"
}

In order to verify that there is something at least listening to that port you can use putty or telnet in a linux shell. Your masternode list full contains the IP address of your masternode at the end of the line. You will want to use that in order to check on your masternode.

telnet 104.236.58.131 13333

Trying 104.236.58.131...

Connected to 104.236.58.131.

Escape character is '^]'.

If you get a response like above, then the daemon is listening on port 13333 for your masternode.

telnet 104.236.58.131 13333

Trying 104.236.58.131...

telnet: Unable to connect to remote host: Connection refused

If you get a response similar to above, or the connection is closed right away in putty, then your daemon is not running, or is firewalled and cannot accept incoming connections.

If you are able to connect to the daemon, then proceed with further diagnostics on this page. If you cannot connect to the daemon, then you need to determine why that is (firewall rules, daemon may have crashed, OOM condition due to low memory on the VPS, etc)

Login to the VPS, and run "./terracoin-cli mnsync status" if that comes back with "IsSynced": true, then issue a "./terracoin-cli masternode debug". If it does not come back with IsSynced true then you need to wait for the daemon on the VPS to finish sync'ing the masternode data.

==Missing Masternode Input==

If the "./terracoin-cli masternode debug" comes back with "Missing masternode input", then you need to check the ~/.terracoincore/terracoin.conf on your server. (You can usually run a "cat ~/.terracoincore/terracoin.conf" to check the contents of the file). Make sure that you have lines similar to:

masternode=1

masternodeprivkey=5JTGQYU94eTaasEbNDFPdZR3negetaVSSoLrM9Z2vjJnG9Y9KCT

masternodeprivkey would be what you got from "masternode genkey" when following the tutorial on setting the masternode up.
If you do not have those lines in the file, then that is your issue, and you would need to put the proper values in that file (using an editor such as nano or similar.

Masternode Diagnostics

2017-11-14T16:30:49Z

SixOfFive: Created page with "This page is a work in progress. More details will appear as further issues are diagnosed. So you followed a tutorial or a script, setup your masternode and boom! It doesn't..."

This page is a work in progress. More details will appear as further issues are diagnosed.

So you followed a tutorial or a script, setup your masternode and boom! It doesn't work. Why?

Check your masternode outputs (in debug console with the Qt wallet you can issue a "masternode outputs"). If nothing comes back except a couple of {} brackets, then you don't have 5000 TRC in a single transaction into that wallet. It cannot be multiple transactions that equals 5000 TRC, it must be 1 transaction of exactly 5000 TRC+network fee. Even if you transferred more (such as 5000.00000001 TRC, that is not exactly 5000 TRC and it will not work).

If you have a value returned, then you need to check the output on the masternode network to see the status of that. Do a "masternode list full output" where output is your output that was listed above when you ran masternode outputs.

masternode list full c313907f484140b1c92fd438dd1263639a7b97f523dfd7370ffff54c9d4dc5aa
{
"c313907f484140b1c92fd438dd1263639a7b97f523dfd7370ffff54c9d4dc5aa-1": " ENABLED 70206 17eqUknFNbFSFcuqDS8XnX4xqt5n1x3UBm 1510674967 207656 1510668460 1116315 104.236.58.131:13333"
}

In order to verify that there is something at least listening to that port you can use putty or telnet in a linux shell. Your masternode list full contains the IP address of your masternode at the end of the line. You will want to use that in order to check on your masternode.

telnet 104.236.58.131 13333

Trying 104.236.58.131...

Connected to 104.236.58.131.

Escape character is '^]'.

If you get a response like above, then the daemon is listening on port 13333 for your masternode.

telnet 104.236.58.131 13333

Trying 104.236.58.131...

telnet: Unable to connect to remote host: Connection refused

If you get a response similar to above, or the connection is closed right away in putty, then your daemon is not running, or is firewalled and cannot accept incoming connections.

If you are able to connect to the daemon, then proceed with further diagnostics on this page. If you cannot connect to the daemon, then you need to determine why that is (firewall rules, daemon may have crashed, OOM condition due to low memory on the VPS, etc)

Login to the VPS, and run "./terracoin-cli mnsync status" if that comes back with "IsSynced": true, then issue a "./terracoin-cli masternode debug". If it does not come back with IsSynced true then you need to wait for the daemon on the VPS to finish sync'ing the masternode data.

==Missing Masternode Input==

If the "./terracoin-cli masternode debug" comes back with "Missing masternode input", then you need to check the ~/.terracoincore/terracoin.conf on your server. (You can usually run a "cat ~/.terracoincore/terracoin.conf" to check the contents of the file). Make sure that you have lines similar to:

masternode=1

masternodeprivkey=5JTGQYU94eTaasEbNDFPdZR3negetaVSSoLrM9Z2vjJnG9Y9KCT

masternodeprivkey would be what you got from "masternode genkey" when following the tutorial on setting the masternode up.
If you do not have those lines in the file, then that is your issue, and you would need to put the proper values in that file (using an editor such as nano or similar.