[ANN] (QTUM) - A Scalable Smart Contract Platform w/ Proof of Stake

[Qtum]

[1715268650]

1715268650

[1715268650]

1715268650

[1715268650]

1715268650

[1715268650]

1715268650

[BTCspace]

that's great!

Qtum to the moon.   

[BTCspace]

What is ico price ?

$0.3

the ico price doesn't matter, just check Eth ico price.

in 1 month, Qtum will be 20$ per coin.

I think it will be closer to 25$

really, i only hope 20$ too..

do not know if it will go to 25$..

[iandoZ]

Do not sell your qtum ... the release of the testnet will spill away any sort of doubt and finally you will get a blockchain 2.0
A single reference for the major coins..20-30-40-100 $ soon...just a little bit of patience

[BTCspace]

Do not sell your qtum ... the release of the testnet will spill away any sort of doubt and finally you will get a blockchain 2.0
A single reference for the major coins..20-30-40-100 $ soon...just a little bit of patience

First POS Smart Contact platform Which is compatible with bitcoin ecosystem?

here you go!

 

[BTCspace]

if Qtum can not be a top5 coin on coinmarketcap by April 9th 2018.

i will give 10BTC to who bet with me.

i posted this before qtum start trading

still valid.

the betting still valid.

still valid.

still valid.

welcome to message me.

[BlockHedge]

if Qtum can not be a top5 coin on coinmarketcap by April 9th 2018.

i will give 10BTC to who bet with me.

i posted this before qtum start trading

still valid.

the betting still valid.

still valid.

still valid.

welcome to message me.

Top 5 right now would require more than $2 billion market cap.  With an initial circulating supply of 51 million tokens, that is about $40 each.  Very possible.  I will not be taking this bet 

[Qtum]

Update:

Starting right now, there will be a large amount of development updates as we near the June 28th release date of the Test Network. These will be technical in nature, but explains the work going into Qtum Core.

We'll start with the first few portions:





1, Qtum Core Branding


Basic Qtum Branding

Basic renaming of the Bitcoin code to make it into Qtum. This shouldn't be too extensive, but should cover the following:

1. Use ~/.qtum instead of ~/.bitcoin for data directory by default
2. Build system should output qtumd instead of bitcoind/cli etc


2, The Basic Qtum Network


Create basic Qtum network

Change the parameters so that the Qtum network is different from Bitcoin.


1. Change genesis seed

2. Change P2P/RPC ports

3. Change "magic" P2P network bytes.

4. Add whatever changes are needed so that a new mainnet network can be mined and synced.

5. Remove bitcoin checkpoints and node lists

6. Make sure that all 3 networks work: mainnet, testnet, and regtest. With mainnet and testnet being distinctly different and incompatible with Bitcoin
Make sure to remove irrelevant tests that only affect Bitcoin, and to change tests which rely on network parameters

specific params:
Block time: 128 seconds
Block size: 2Mb
P2P port: 3888 (chosen arbitrarily, shouldn't have conflicts, but can be changed if needed)
RPC port: 3889
testnet P2P port: 13888
testnet RPC port: 13889
Qtum pubkeyhash address: 58 (Q)
Qtum p2sh address: 50 (M)
Qtum testnet p2pkh: 120 (q)
Qtum testnet p2sh: 110 (m)



3, Add EVM and OP_CREATE for Contract Execution


After this, the EVM should be integrated and a very basic contract should be executable.

There will be a new opcode, OP_CREATE (formerly OP_EXEC), which takes 4 arguments, in push order:
1. VM version (currently 1 is EVM)
2. Gas price (not yet used, anything is valid)
3. Gas limit (not yet used, assume very high limit)
4. bytecode


For now it is OK that this script format be forced and mandatory for OP_CREATE transactions on the blockchain. (ie, only "standard" allowed on the blockchain)
When OP_CREATE is encountered, it should execute the EVM and persist the contract to a database (triedb)


Note:
Make sure to follow policy for external code (commit vanilla unmodified code first, and then change it as needed)
Make the EVM test suite functional as well (someone else can setup continuous integration changes for it though)


QTUM Address for new contracts


QTUmCORE-3. Test that qtum address is generated after contract creation. Before running the test make sure that:

Node started в –regtest
Bitcoin tests passed
Test Steps


1. Create transaction TX_DEPLOYMENT in bitcoinlib-js, run decoderawtransaction.
2. Create transaction TX_ASSIGN_SC in bitcoinlib-js, run decoderawtransaction.
3. Create transaction TX_DEPLOYMENT in bitcoinlib-js, run sendrawtransaction.
3. Create transaction TX_ASSIGN_SC in bitcoinlib-js, run sendrawtransaction.


Expected Result
1. Transaction marked as deployment.
2. Transaction marked as assign.
3. Contract created (address and balance are displayed on the console).
4. Contract state changed (address and balance are displayed on the console).




4, Add PoS block verification and mining






After this, the Qtum blockchain should be capable of verifying basic PoS v3 blocks, and the wallet should be able to mine these blocks similar to PoW blocks.

There is not a network rule as of yet for only allowing PoS blocks at this point, so the chain will accept either PoW and PoS blocks as valid. Both block types should use the same default bitcoin standard difficulty.


Thing to ensure:


1, stake modifier changes every block  

2, Coinage does not change PoS values

3, No decentralized checkpoints (still in design)

4, Make sure that these statements remain true:

5, don't enforce tx fee as consensus rule

6, static pos reward (make it just 1 token for now, will change later)

7, stake modifier v2 - The purpose of stake modifier is to prevent a txout (coin) owner from computing future proof-of-stake generated by txout at the time of transaction confirmation. Verification of the block was changed, now you need only previous block, so all other blocks can be deleted and space saved  (you need last 500 blocks to stake) pruning capabilities should be in future major release

8, compatibility with BIP66

9, only last 500 blocks are needed to verify proof of stake

10, No coin age, instead just a coin confirmation requirement (500 blocks is fine for now)



5, Add ability for contracts to call other deployed contracts




Contracts should be capable of calling other contracts using a new opcode, OP_CALL.

Arguments in push order:
version (32 bit integer)
gas price (64 bit integer)
gas limit (64 bit integer)
contract address (160 bits)
data (any length)
OP_CALL should ways return false for now.


OP_CALL only results in contract execution when used in a vout; Similar to OP_CREATE, it uses the special rule to process the script during vout processing (rather than when spent as is normal in Bitcoin). Contract execution should only be triggered when the transaction script is in this standard format and has no extra opcodes.

If OP_CALL is created that uses an invalid contract address, then no contract execution should take place. The transaction should still be valid in the blockchain however. If money was sent with OP_CALL, then that money (minus the gas fees) should result in a refund transaction to send the funds back to vin[0]'s vout script.

The "sender" exposed to EVM should be the pubkeyhash spent by vin[0]. If the vout spent by vin[0] is not a pubkeyhash, then the sender should be 0.

Funds can be sent to the contract using an OP_CALL vout. These funds will be handled by the account abstraciton layer in a different story, to expose this to the EVM.
Multiple OP_CALLS can be used in a single transaction. However, before contract execution, the gas price and gas limit of each OP_CALL vout should be checked to ensure that the transaction provides enough transaction fees to cover the gas. Additionally, this should be verified even when the contract is not executed, such as when it is accepted in the mempool.





These updates should give you an idea of what we are working on leading up to the June 28th release of the Test Network. Please see the Roadmap below for more information:

Please remember that we have an event in Shanghai on the 28th so please RSVP if you plan on attending:

[BTCspace]

Update:

Starting right now, there will be a large amount of development updates as we near the June 28th release date of the Test Network. These will be technical in nature, but explains the work going into Qtum Core.

We'll start with the first few portions:





1, Qtum Core Branding


Basic Qtum Branding

Basic renaming of the Bitcoin code to make it into Qtum. This shouldn't be too extensive, but should cover the following:

1. Use ~/.qtum instead of ~/.bitcoin for data directory by default
2. Build system should output qtumd instead of bitcoind/cli etc


2, The Basic Qtum Network


Create basic Qtum network

Change the parameters so that the Qtum network is different from Bitcoin.


1. Change genesis seed

2. Change P2P/RPC ports

3. Change "magic" P2P network bytes.

4. Add whatever changes are needed so that a new mainnet network can be mined and synced.

5. Remove bitcoin checkpoints and node lists

6. Make sure that all 3 networks work: mainnet, testnet, and regtest. With mainnet and testnet being distinctly different and incompatible with Bitcoin
Make sure to remove irrelevant tests that only affect Bitcoin, and to change tests which rely on network parameters

specific params:
Block time: 128 seconds
Block size: 2Mb
P2P port: 3888 (chosen arbitrarily, shouldn't have conflicts, but can be changed if needed)
RPC port: 3889
testnet P2P port: 13888
testnet RPC port: 13889
Qtum pubkeyhash address: 58 (Q)
Qtum p2sh address: 50 (M)
Qtum testnet p2pkh: 120 (q)
Qtum testnet p2sh: 110 (m)



3, Add EVM and OP_CREATE for Contract Execution


After this, the EVM should be integrated and a very basic contract should be executable.

There will be a new opcode, OP_CREATE (formerly OP_EXEC), which takes 4 arguments, in push order:
1. VM version (currently 1 is EVM)
2. Gas price (not yet used, anything is valid)
3. Gas limit (not yet used, assume very high limit)
4. bytecode


For now it is OK that this script format be forced and mandatory for OP_CREATE transactions on the blockchain. (ie, only "standard" allowed on the blockchain)
When OP_CREATE is encountered, it should execute the EVM and persist the contract to a database (triedb)


Note:
Make sure to follow policy for external code (commit vanilla unmodified code first, and then change it as needed)
Make the EVM test suite functional as well (someone else can setup continuous integration changes for it though)


QTUM Address for new contracts


QTUmCORE-3. Test that qtum address is generated after contract creation. Before running the test make sure that:

Node started в –regtest
Bitcoin tests passed
Test Steps


1. Create transaction TX_DEPLOYMENT in bitcoinlib-js, run decoderawtransaction.
2. Create transaction TX_ASSIGN_SC in bitcoinlib-js, run decoderawtransaction.
3. Create transaction TX_DEPLOYMENT in bitcoinlib-js, run sendrawtransaction.
3. Create transaction TX_ASSIGN_SC in bitcoinlib-js, run sendrawtransaction.


Expected Result
1. Transaction marked as deployment.
2. Transaction marked as assign.
3. Contract created (address and balance are displayed on the console).
4. Contract state changed (address and balance are displayed on the console).




4, Add PoS block verification and mining






After this, the Qtum blockchain should be capable of verifying basic PoS v3 blocks, and the wallet should be able to mine these blocks similar to PoW blocks.

There is not a network rule as of yet for only allowing PoS blocks at this point, so the chain will accept either PoW and PoS blocks as valid. Both block types should use the same default bitcoin standard difficulty.


Thing to ensure:


1, stake modifier changes every block  

2, Coinage does not change PoS values

3, No decentralized checkpoints (still in design)

4, Make sure that these statements remain true:

5, don't enforce tx fee as consensus rule

6, static pos reward (make it just 1 token for now, will change later)

7, stake modifier v2 - The purpose of stake modifier is to prevent a txout (coin) owner from computing future proof-of-stake generated by txout at the time of transaction confirmation. Verification of the block was changed, now you need only previous block, so all other blocks can be deleted and space saved  (you need last 500 blocks to stake) pruning capabilities should be in future major release

8, compatibility with BIP66

9, only last 500 blocks are needed to verify proof of stake

10, No coin age, instead just a coin confirmation requirement (500 blocks is fine for now)



5, Add ability for contracts to call other deployed contracts




Contracts should be capable of calling other contracts using a new opcode, OP_CALL.

Arguments in push order:
version (32 bit integer)
gas price (64 bit integer)
gas limit (64 bit integer)
contract address (160 bits)
data (any length)
OP_CALL should ways return false for now.


OP_CALL only results in contract execution when used in a vout; Similar to OP_CREATE, it uses the special rule to process the script during vout processing (rather than when spent as is normal in Bitcoin). Contract execution should only be triggered when the transaction script is in this standard format and has no extra opcodes.

If OP_CALL is created that uses an invalid contract address, then no contract execution should take place. The transaction should still be valid in the blockchain however. If money was sent with OP_CALL, then that money (minus the gas fees) should result in a refund transaction to send the funds back to vin[0]'s vout script.

The "sender" exposed to EVM should be the pubkeyhash spent by vin[0]. If the vout spent by vin[0] is not a pubkeyhash, then the sender should be 0.

Funds can be sent to the contract using an OP_CALL vout. These funds will be handled by the account abstraciton layer in a different story, to expose this to the EVM.
Multiple OP_CALLS can be used in a single transaction. However, before contract execution, the gas price and gas limit of each OP_CALL vout should be checked to ensure that the transaction provides enough transaction fees to cover the gas. Additionally, this should be verified even when the contract is not executed, such as when it is accepted in the mempool.





These updates should give you an idea of what we are working on leading up to the June 28th release of the Test Network. Please see the Roadmap below for more information:

Please remember that we have an event in Shanghai on the 28th so please RSVP if you plan on attending:

that's really great!

thanks for the updates, looking forward the testnet release next week!

[onetwo12]

Quote from: skycoin on March 16, 2017, 04:54:31 PM

- https://qtum.org

Qtum, will probably replace ethereum because it is simpler and has fewer problems. The UXTO model is much cleaner. They have a lot of previous developers and have already done two previous coins and are the best team I have seen so far.


I won't trust dev that promoting qtum-SCAM.....

I have not looked at qtum's code.

We know the qtum founder and he is one of the largest investors in Skycoin from four years ago, before qtum or any of this. Some of the people around him are legendary scammers, but he is not a scammer.

I think Patricks role in the bitbay situation is exaggerated. I read through the arguments and it just sounds like drama.

Many of the people in the Bitcoin community are sociopaths. They often steal things or cause drama, then immediately blame it or scapegoat it on someone else. They are not even done stealing the money, before they go on campaign of moral indignation against the fall person.

I think Patrick was blamed for Bitbay because his personality makes him an easy victim for sociopaths and the human predators in the bitcoin community. There are people walking around, sizing people up and trying to determine whether they can manipulate someone, setup a scam, steal things and who is going to be gullible or a fall person.

If you knew the people involved, you would understand what the social dynamic is.

>Also how can you be so confident qtum is going to replace ETH based on it's tech when they haven't released code yet?

Ethereum is using an accounts model, like Ripple. Which is anti-blockchain and anti-privacy and very traceable. It is against the philosophy of Bitcoin.

All coins going forward will be on the UXTO model and it is best practice for blockchain. Moving turing complete smart contracts off of accounts model and onto UXTO is extremely important and that is what qtum appears to be doing.

We need to figure out how to do general computation on a UXTO model. Instead of being restrained to the Ripple/Ethereum accounts model.

I think they will get closer to the goal, but only get there part way
- thin client for smart contracts (major limitation for existing system)
- moving smart contracts onto UXTO (major milestone)

I do not know if qtum has succeeded, but they seem to be going in right direction. I talked to one of their technical leads and they were focused on "Getting it working with something we can do now" and then incremental improvement over time. So first implementing the Ethereum virtual machine on top of UXTO, then working out the research problems for a native turing complete UXTO language later.

I do not know if there is a way to full UXTO while still having "gas". I think you will need to get rid of the "gas". In the ethereum model to take full advantage. I do not know if qtum will be able to go far enough in doing that, but is heading in the correct direction.

Ethereum tries to be both a token and a computer.
- we started with pure tokens (Bitcoin)
- then we added a computer to the tokens (Ethereum)
- now we just trying to figure out how to build  pure computer on UXTO
- Then once we have the computer, the tokens or coins just become a program or entity running on this "distributed computer"

Bitcoin, Ethereum, qtum, byteballs, etc are just stepping stones. Towards a final solution. None of these will exist or be relevant in ten years. We are in an age of transition and I am looking at the projects that are getting closer to the goal, in a pure mathematical sense.

Even Skycoin is being ripped up and its foundations constantly rewritten when it is advantageous to do so. Bitcoin is static and relatively unchanging, while Ethereum has been able to get the community to accept constant small changes.

Skycoin is on a punctuated equilibrium model, where we do bug fixes and polishing, then completely rip up and rebuild the foundation as needed, then go back to bug fixes and polishing.

Right now, we are exploring new networking primitives and the advantage of immutable data structures, but are still on blockchain. Putting EVM on UXTO is heading towards immutable data structures from the perspective of computation, while we are heading towards immutable data structures from the path of consensus, networking and simplifying object synchronization protocols.

One of the pilots that is being spun out of that project is the distibuted, peer-to-peer social media platform built upon immutable data structures and peer-to-peer object replication. For this Skycoin chose a public key, cryptographic publisher/subscriber model and DAG immutable object tree. While Ethereum's project chose a Kadmelia DHT block storage model.

Ignoring the individuals and the drama, I am just looking at the "future direction" and who is heading in that direction.

>Also how can you be so confident qtum is going to replace ETH based on it's tech when they haven't released code yet?

I am not confident it will replace Ethereum. At the start, it will be equivalent to ethereum in terms of being able to run the Ethereum Virtual Machine (EVM) on top of qtum with UXTO. Then they will do a native language.

It will depend on the implementation. I do not know if qtum has succeeded, but they seem to be going in right direction.

Similarly, Byteballs may fail or may not exist in ten years, but they are pioneering the first experiments into replacing the Blockchain with a DAG. Which we have been considering for several years now.

Similarly, Bitcoin was the first but people are getting used to the idea that it will not be the final or best cryptocurrency. That it was just the first generation and that we can build better and improve it substantially.



thank you skycoin dev, because of you, i brought into qtum and made some money.

i like this post, everyone should read it.

that's one of the most exciting post this year.

yes that's a good post for sure.

[meccaflare0]

Quote from: skycoin on March 16, 2017, 04:54:31 PM

- https://qtum.org

Qtum, will probably replace ethereum because it is simpler and has fewer problems. The UXTO model is much cleaner. They have a lot of previous developers and have already done two previous coins and are the best team I have seen so far.


I won't trust dev that promoting qtum-SCAM.....

I have not looked at qtum's code.

We know the qtum founder and he is one of the largest investors in Skycoin from four years ago, before qtum or any of this. Some of the people around him are legendary scammers, but he is not a scammer.

I think Patricks role in the bitbay situation is exaggerated. I read through the arguments and it just sounds like drama.

Many of the people in the Bitcoin community are sociopaths. They often steal things or cause drama, then immediately blame it or scapegoat it on someone else. They are not even done stealing the money, before they go on campaign of moral indignation against the fall person.

I think Patrick was blamed for Bitbay because his personality makes him an easy victim for sociopaths and the human predators in the bitcoin community. There are people walking around, sizing people up and trying to determine whether they can manipulate someone, setup a scam, steal things and who is going to be gullible or a fall person.

If you knew the people involved, you would understand what the social dynamic is.

>Also how can you be so confident qtum is going to replace ETH based on it's tech when they haven't released code yet?

Ethereum is using an accounts model, like Ripple. Which is anti-blockchain and anti-privacy and very traceable. It is against the philosophy of Bitcoin.

All coins going forward will be on the UXTO model and it is best practice for blockchain. Moving turing complete smart contracts off of accounts model and onto UXTO is extremely important and that is what qtum appears to be doing.

We need to figure out how to do general computation on a UXTO model. Instead of being restrained to the Ripple/Ethereum accounts model.

I think they will get closer to the goal, but only get there part way
- thin client for smart contracts (major limitation for existing system)
- moving smart contracts onto UXTO (major milestone)

I do not know if qtum has succeeded, but they seem to be going in right direction. I talked to one of their technical leads and they were focused on "Getting it working with something we can do now" and then incremental improvement over time. So first implementing the Ethereum virtual machine on top of UXTO, then working out the research problems for a native turing complete UXTO language later.

I do not know if there is a way to full UXTO while still having "gas". I think you will need to get rid of the "gas". In the ethereum model to take full advantage. I do not know if qtum will be able to go far enough in doing that, but is heading in the correct direction.

Ethereum tries to be both a token and a computer.
- we started with pure tokens (Bitcoin)
- then we added a computer to the tokens (Ethereum)
- now we just trying to figure out how to build  pure computer on UXTO
- Then once we have the computer, the tokens or coins just become a program or entity running on this "distributed computer"

Bitcoin, Ethereum, qtum, byteballs, etc are just stepping stones. Towards a final solution. None of these will exist or be relevant in ten years. We are in an age of transition and I am looking at the projects that are getting closer to the goal, in a pure mathematical sense.

Even Skycoin is being ripped up and its foundations constantly rewritten when it is advantageous to do so. Bitcoin is static and relatively unchanging, while Ethereum has been able to get the community to accept constant small changes.

Skycoin is on a punctuated equilibrium model, where we do bug fixes and polishing, then completely rip up and rebuild the foundation as needed, then go back to bug fixes and polishing.

Right now, we are exploring new networking primitives and the advantage of immutable data structures, but are still on blockchain. Putting EVM on UXTO is heading towards immutable data structures from the perspective of computation, while we are heading towards immutable data structures from the path of consensus, networking and simplifying object synchronization protocols.

One of the pilots that is being spun out of that project is the distibuted, peer-to-peer social media platform built upon immutable data structures and peer-to-peer object replication. For this Skycoin chose a public key, cryptographic publisher/subscriber model and DAG immutable object tree. While Ethereum's project chose a Kadmelia DHT block storage model.

Ignoring the individuals and the drama, I am just looking at the "future direction" and who is heading in that direction.

>Also how can you be so confident qtum is going to replace ETH based on it's tech when they haven't released code yet?

I am not confident it will replace Ethereum. At the start, it will be equivalent to ethereum in terms of being able to run the Ethereum Virtual Machine (EVM) on top of qtum with UXTO. Then they will do a native language.

It will depend on the implementation. I do not know if qtum has succeeded, but they seem to be going in right direction.

Similarly, Byteballs may fail or may not exist in ten years, but they are pioneering the first experiments into replacing the Blockchain with a DAG. Which we have been considering for several years now.

Similarly, Bitcoin was the first but people are getting used to the idea that it will not be the final or best cryptocurrency. That it was just the first generation and that we can build better and improve it substantially.



thank you skycoin dev, because of you, i brought into qtum and made some money.

i like this post, everyone should read it.

that's one of the most exciting post this year.

yes that's a good post for sure.

I will the event be streamed or uploaded in anyway?

[Qtum]

The last time we did an event in Shanghai it was streamed, but we used a Chinese service.  We can try to upload it for others to see if streaming isn't possible for Western audiences.

[Qtum]

Test Network Update #2:

Leading up to our June 28th Test Network release, we will be providing daily updates that explain the work that goes on behind the scenes. Yesterday we went over the first 5 points, and today we delve deeper into the technical aspects.





6, Add "sendtocontract" RPC call




An rpc call should be adding for sending data and (optionally) money to a contract that has been deployed on the blockchain.

The format should be:
sendtocontract contract-address data (value gaslimit gasprice sender broadcast)

This should create a contract call transaction using OP_CALL.
Value defaults to 0.

sender-address is optional. If no address is specified, then it should be picked randomly from the wallet. If no outputs exist to spend using that sender-address, then an error should be shown and no transaction created.
broadcast should default to true. If broadcast is false, then the transaction is created and signed, and then printed to the screen in hex rather than broadcast to the network.

If the sender-address does have an output, but it is not enough to cover the gas costs, tx fees, and value, then any UTXO owned by the wallet should be used by the transaction to cover the remainder. (not all funds must come from sender-address, but the sender-address must be vin[0])

After execution, if broadcast is true, it should print the txid and the new contract address.


7, Add "callcontract" RPC call for off-chain computations


Add "callcontract" RPC call for off-chain computations

There should be an RPC call that executes a contract without requiring interaction with the blockchain network, and thus without gas or other fees.

callcontract contract-address data (sender)
This should execute the contract locally, and if the contract function returns data, it should be returned/printed by the RPC call. Sender is optional and does not require an owned vout (it can be any valid address)






8, Change mainnet to only allow PoS after a certain blockheight


This tells the Blockchain that Proof-of-Work blocks can no longer be accepted. The Qtum Nodes will reject this work, and accept only Proof-of-Stake.




9 , Put EVM "LOG" opcode outputs into an accessible log file



There should be a file that holds all of the data from EVM LOG opcodes, so that it can be used for testing and debugging. There are ITDs written for this
The log file should only be used when `-record-log-opcodes` is passed into qtumd


10, Setup continuous integration



Setup a Jenkins server and make it so that it does:

1. Automatically builds qtum on all branches on Linux and reports build errors
2. Automatically runs the Qtum (Bitcoin) test suite, reporting any failing tests
3. Tears down any VMs constructed to ensure we don't use more VM time than necessary







Please see the Roadmap below for more information:

Please remember that we have an event in Shanghai on the 28th so please RSVP if you plan on attending:

Qtum will also be sponsoring a Hackathon in Russia, with 8500 QTUM tokens. For more information, please see:

http://blockchainhack.ru/

[thesavoyard]

Is the crowdsale still on?

[Qtum]

Is the crowdsale still on?

The Crowdsale ended on March 21st, but the test network will be released on June 28th, allowing you to acquire test tokens and check out the system. The main network launches in September, which is when participants can withdraw their coins from the exchanges.

[thesavoyard]

Is the crowdsale still on?

The Crowdsale ended on March 21st, but the test network will be released on June 28th, allowing you to acquire test tokens and check out the system. The main network launches in September, which is when participants can withdraw their coins from the exchanges.

So we currently cannot buy tokens from people who bought them in the crowdsale? What's the price of the testnet, is it similar to crowdsale?

[Qtum]

Is the crowdsale still on?

The Crowdsale ended on March 21st, but the test network will be released on June 28th, allowing you to acquire test tokens and check out the system. The main network launches in September, which is when participants can withdraw their coins from the exchanges.

So we currently cannot buy tokens from people who bought them in the crowdsale? What's the price of the testnet, is it similar to crowdsale?

Test Network tokens are free, we will send them to whoever downloads a wallet and requests them.  We ask that anyone who does this submits any bugs they encounter, even if it's a typo.

For purchasing tokens before the main network launches, some exchanges have opened IOU trading, but you will not be able to withdraw them until September.

Please see our position on Futures / IOU trading here:

https://qtum.org/en/blog/qtum-team-s-position-on-activating-qtum-trading

[Gleb Gamow]

Is the crowdsale still on?

The Crowdsale ended on March 21st, but the test network will be released on June 28th, allowing you to acquire test tokens and check out the system. The main network launches in September, which is when participants can withdraw their coins from the exchanges.

So we currently cannot buy tokens from people who bought them in the crowdsale? What's the price of the testnet, is it similar to crowdsale?

Test Network tokens are free, we will send them to whoever downloads a wallet and requests them.  We ask that anyone who does this submits any bugs they encounter, even if it's a typo.

For purchasing tokens before the main network launches, some exchanges have opened IOU trading, but you will not be able to withdraw them until September.

Please see our position on Futures / IOU trading here:

https://qtum.org/en/blog/qtum-team-s-position-on-activating-qtum-trading

<this is not a dis post>

You bastard!  You know that I strive to be as grammatically correct as possible, hence possibly now catering to my inner Grammar Nazi.  Humor aside, I truly like what's highlighted above. 

Keep up the good work while I try to keep my negative comments to a minimum.

One more thing: IT REALLY PISSES ME OFF THAT YOU'VE NOT ONCE DELETED ANY OF MY POSTS!

Note to self: Try harder. 

Bruno

[testerx]

Haha, I had some time off last week, too bad am super busy with work next week or I'd have flown to Shanghai for this launch.  Think I made more from investing in the Qtum ICO than my job though.
Can't wait to try out the testnet.

[ada84]

8th highest traded coin in the world today.