What Is gAsp (GASP)?
Aspire embeds data into regular gAsp blockchain transactions. To a regular client, these transactions look like normal gAsp transactions, with one party sending another party a very small amount. An Aspire node (which runs the client along with the Aspire client software will recognize and interpret the data in these transactions based on specific rules. From this, it constructs its own ledger of Aspire transactions that it has seen on the network. Another way to think of it is similar to a Russian nesting doll, where the bigger doll would be the transaction, and the next doll (inside of it) would be a Aspire transaction.
This embedding method is technically known as embedded consensus. gAsp is a Proof of Work blockchain that uses scrypt mining and advanced checkpoint technology. This is the combination of several cryptocurrency technologies combined together. In the source code of you will find original code from Bitcoin, Litecoin, Unbreakable Coin, Peercoin, and eVoxels, and eBoost. You will also find the latest features in crypto technology such as ACP, Segwit, and the RPC used by third party services such as exchanges.
gAsp Storage Key Points
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
How do the Aspire nodes stay in sync? What’s to stop one node from disagreeing with another?
As all Aspire nodes run the same code, and all receive the same gAsp transaction data, the ledgers across each node match exactly. Aspire nodes are not like nodes in that they don’t communicate with each other: they simply connect to the software and download transactions from it, decoding each one as they go along. In this way, the immense security and computing power behind is leveraged as the “transport network” for Aspire data. Given the above, there is no “Aspire peer to peer network” like there is a “Gasp peer-to-peer network”: Aspire-aware nodes comprise a subset of the Gasp full nodes in existence.
What about Side chains?
Aspire is optimal for mainly higher value transactions and greatly benefits from the security of the main chain. However, if side chains are ever released, there is no reason that they couldn’t be made to work with Aspire. This is the beauty of Aspire’s embedded consensus technology – it can work with just about any blockchain out there, including side chain designs.
What is ASP?
gAsp is the native asset (token) of Aspire and some ASP (currently 10) is required as the fee to create new assets on Aspire. It is a technical necessity for adding advanced features to Aspire, which by nature require a protocol aware asset. They can only be aware, while Aspire can be aware of both and ASP itself as well as all assets created on Aspire.
Is a 51% attack against Aspire possible?
The short answer is no 51% attacks are not possible on Aspire. The gAsp blockchain utilizes advanced checkpoint technology (ACP) to prevent blockchain hijacking, 51% attacks and double spending. This feature also makes it impossible to perform a rollback on the blockchain. In the past Ethereum has rolled back the blockchain due to a DAO smart contract exploit. In this case of Ethereum, the rollback caused a fork into two chains which are now known as Ethereum and Ethereum Classic. This type of roll back is not possible with Aspire or it’s underlying blockchain.
Besides a 51% attack, what are the other risks to consensus?
The Aspire network could be effectively “forked” by a sizable number of people running different versions of the Aspire client that had different “consensus sensitive code” (i.e. protocol code). In this case, if a transaction was read in from the gAsp client software, the differing code may cause two different interpretations of the data, and thus, two different ledger states.
As long as all participants run software that has the same protocol rules (even if it is different Aspire client implementations), this situation will not happen. The reference client includes extensive safeguards that help detect and prevent this from happening. This new ledger would not be “Aspire”. It would be a separate ledger with its own protocol rules. Services built on this ledger would not agree with similar services built on the Aspire ledger.
That being said, the Aspire client is completely open-source. Anyone is able to copy the code and make their own modifications. They can then run their modified version of the software, which technically may generate a different ledger than everyone else. This is similar to Bitcoin itself and Bitcoin Cash. gAsp have any impact, that person would have to get others to run it, who would have to trust this individual more than they trust the Aspire development team.