when will it start ?
i can't wait to see it's come out
Topic: [ANN] TIMEREUM (TME) VERSION 2.0: "ELIXIR" (ELIX) RELEASED (NEW THREAD) - page 125. (Read 126691 times)
July 15, 2017, 08:58:56 AM
July 15, 2017, 08:57:48 AM
If we're so impatient, timereum will be dumped immediately after it's listed. The supply in the future will be reduced but... what should I do? 
July 15, 2017, 07:42:21 AM
Right we have to be patient because this is "timereum". The more time we wait, the more treasure we get 
yeah time is money lol but the contract is not deployed yet so you earn nothing 
July 15, 2017, 06:30:39 AM
Give the dev some rest. It is weekend after all. Waiting will be one of the key traits with this coin anyway.
HOW DO YOU KNOW ABOUT KEY TRAITS?AND IT IS MY WEEKEND TOO. ALL I NEED IS TO CHILL OUT AND TOUCH MY JOHNSON. HE NEEDS TO WORK.
ARE YOU GERMAN?
July 15, 2017, 06:10:46 AM
Give the dev some rest. It is weekend after all. Waiting will be one of the key traits with this coin anyway.
July 15, 2017, 06:03:14 AM
Right we have to be patient because this is "timereum". The more time we wait, the more treasure we get
July 15, 2017, 05:44:57 AM
I hope at least today, Timereum go Live.
We all are waiting for it.
We all are waiting for it.
Haha, why so impatient? Give them a week or 2 to test everything. 1 small mistake in a contract code will result in a dead project...
July 15, 2017, 04:02:25 AM
-The following sentences comes from the whitepaper : "The first ten transactions from a child to its parent triggers the generation of currency in the child."
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
The rate increases from 25% to 100% in a linear function, which means first year 25% second year will be 33.33%, 3rd year will be 41.66% , 4th year will be 0.5% and so on (increasing by 08.33% every year, or 0.02283105% every day)
So the longer you hold, the more coins you can generate.
You also can generate 10 times only, so if you use only 1 token generating transfer (from your child address to parent) the first year, you can wait more and generate again 9 times with a higher rate (depending on how much you wait).
As for the solution the dev found about pairing all of our addresses together and removing the need to double addresses, I find it very smart actually, because the parent address is playing the role of a key to unlock the tokens in the child address therefore we don't really need access to the parent address. Good solution dev.
If i understand, we can retry 1.14 coins each day. this coins and airdrop is very interresting, but it need gas for transaction
July 15, 2017, 01:31:23 AM
I hope at least today, Timereum go Live.
We all are waiting for it.
We all are waiting for it.
July 15, 2017, 01:06:47 AM
i want to see how it work , how it mine .
can't wait it list on exchange .
want to buy some
can't wait it list on exchange .
want to buy some
July 15, 2017, 01:01:43 AM
*snip*
cut
As for the solution the dev found about pairing all of our addresses together and removing the need to double addresses, I find it very smart actually, because the parent address is playing the role of a key to unlock the tokens in the child address therefore we don't really need access to the parent address. Good solution dev.
Thank you very much for your clear reply sir, the one I've been waiting for a long time
.So my noob brain processes like this:
If I am paired with a dead man, I use gas to send ETH/ tokens to his address and it does not have consequences for whatever I send him (I can still access that?) and it generates a mining batch which is send to MY address?
Sorry, just trying to get along here....
I understood so. We get for the very fact of sending a token to the parent address. His actions do not affect us in any way.
July 14, 2017, 11:07:45 PM
*snip*
cut
As for the solution the dev found about pairing all of our addresses together and removing the need to double addresses, I find it very smart actually, because the parent address is playing the role of a key to unlock the tokens in the child address therefore we don't really need access to the parent address. Good solution dev.
Thank you very much for your clear reply sir, the one I've been waiting for a long time
.So my noob brain processes like this:
If I am paired with a dead man, I use gas to send ETH/ tokens to his address and it does not have consequences for whatever I send him (I can still access that?) and it generates a mining batch which is send to MY address?
Sorry, just trying to get along here....
July 14, 2017, 08:39:06 PM
*snip*
The rate increases from 25% to 100% in a linear function, which means first year 25% second year will be 33.33%, 3rd year will be 41.66% , 4th year will be 0.5% and so on (increasing by 08.33% every year, or 0.02283105% every day)
So the longer you hold, the more coins you can generate.
You also can generate 10 times only, so if you use only 1 token generating transfer (from your child address to parent) the first year, you can wait more and generate again 9 times with a higher rate (depending on how much you wait).
As for the solution the dev found about pairing all of our addresses together and removing the need to double addresses, I find it very smart actually, because the parent address is playing the role of a key to unlock the tokens in the child address therefore we don't really need access to the parent address. Good solution dev.
Thank you very much for your clear reply sir, the one I've been waiting for a long time
. July 14, 2017, 06:33:19 PM
-The following sentences comes from the whitepaper : "The first ten transactions from a child to its parent triggers the generation of currency in the child."
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
The rate increases from 25% to 100% in a linear function, which means first year 25% second year will be 33.33%, 3rd year will be 41.66% , 4th year will be 0.5% and so on (increasing by 08.33% every year, or 0.02283105% every day)
So the longer you hold, the more coins you can generate.
You also can generate 10 times only, so if you use only 1 token generating transfer (from your child address to parent) the first year, you can wait more and generate again 9 times with a higher rate (depending on how much you wait).
As for the solution the dev found about pairing all of our addresses together and removing the need to double addresses, I find it very smart actually, because the parent address is playing the role of a key to unlock the tokens in the child address therefore we don't really need access to the parent address. Good solution dev.
I agree, it's a smart solution. If it will allow to make contract code better, just go for it
July 14, 2017, 06:26:47 PM
-The following sentences comes from the whitepaper : "The first ten transactions from a child to its parent triggers the generation of currency in the child."
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
The rate increases from 25% to 100% in a linear function, which means first year 25% second year will be 33.33%, 3rd year will be 41.66% , 4th year will be 0.5% and so on (increasing by 08.33% every year, or 0.02283105% every day)
So the longer you hold, the more coins you can generate.
You also can generate 10 times only, so if you use only 1 token generating transfer (from your child address to parent) the first year, you can wait more and generate again 9 times with a higher rate (depending on how much you wait).
As for the solution the dev found about pairing all of our addresses together and removing the need to double addresses, I find it very smart actually, because the parent address is playing the role of a key to unlock the tokens in the child address therefore we don't really need access to the parent address. Good solution dev.
July 14, 2017, 05:54:39 PM
Rather quick.
I believe MNE dev put in money of his own to get it on livecoin.
Could be wrong
I believe MNE dev put in money of his own to get it on livecoin.
Could be wrong
you are in the wrong thread..that is timereum no MNE!
July 14, 2017, 03:31:13 PM
Why don't you try these with your existing code:
- Continue to refactor into libraries. This is the #1 way to reduce the bytecode size of the main contract.
- Use shorter types for struct elements and sort them such that short types are grouped together. Started doing this and it makes a massive difference even if the code is not as readable or clean looking.
- Move duplicate functionality into generic functions or function modifiers (even if it means more function parameters).
- Instead of creating multiple getters (or multiple public members), create bundled getters that return multiple values at once.
- Use local variables to reference storage array elements.
- Remove some constant functions that are not critical to the contract.
I don't think reducing codes going to help, because of hard-codings the addresses max out the size limit of the smart contract,
that is why he has to pair with another person's address to reduce the size.
I hope Dev could find another workaround rather than pairing with another person's address.
July 14, 2017, 03:30:11 PM
it is very difficult for me. but I think on extent of receipt of information I understand how it works)
July 14, 2017, 03:20:37 PM
-The following sentences comes from the whitepaper : "The first ten transactions from a child to its parent triggers the generation of currency in the child."
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Only transactions from the child to the parent will create coins. You can transfer already mined coins to all addresses but the parent one.
July 14, 2017, 02:54:40 PM
-The following sentences comes from the whitepaper : "The first ten transactions from a child to its parent triggers the generation of currency in the child."
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Does that mean the 9 previous transactions don't allow us to trade the coins deposited using batches ?
-2nd one : "Specifically, the coins per batch created is a linear function that allows 25% of maximum coin generation when the system goes online, and 100% after 10 years"
Does it mean however we hold or use the available batches, we would not be able to get the maximum supply per batch so it will generate at a 25% rate for the 10 next years ? (1250 coins/year).
Jump to: