[EKN] Elektron - EKN - ElektronFoundation TOR MARKET - Bittrex - Cryptsy

[topcat363]

My advice to u dev do not list Elektron to bittrex before pos starts, let the miners dump @ c-cex. Elektron might start with higher price when pos starts @ bittrex

if dev delivers big then miners dumping will have zero affect on the market

[VEL2014]

Waited 10 minutes - wallet is not synchronized

[zmija]

My advice to u dev do not list Elektron to bittrex before pos starts, let the miners dump @ c-cex. Elektron might start with higher price when pos starts @ bittrex

if dev delivers big then miners dumping will have zero affect on the market

that's a BIG "IF". look @ the cypher it was listet on ttrex to soon and now struggling @ 3-4k sat, so if u r a new investor and u c a coin starting price @ let's say 4k then if it goes to 10k everybody will thing it has been allready pumped, but if it starts @ 6-8k then 10k won't look like a pump

[topcat363]

My advice to u dev do not list Elektron to bittrex before pos starts, let the miners dump @ c-cex. Elektron might start with higher price when pos starts @ bittrex

if dev delivers big then miners dumping will have zero affect on the market

that's a BIG "IF". look @ the cypher it was listet on ttrex to soon and now struggling @ 3-4k sat, so if u r a new investor and u c a coin starting price @ let's say 4k then if it goes to 10k everybody will thing it has been allready pumped, but if it starts @ 6-8k then 10k won't look like a pump

i do not agree w this logic.


pumping/ success is way deeper than just an early add.

[ElektronFoundation]

Spread hashes to the other pools too people.

Thanks.

[tm2013]

Any ETA on your updates, dev?

[Digital_Currency_LTD]

Good sign....

https://twitter.com/BittrexExchange/status/588789681803763712

[ElektronFoundation]

guys please spread hash on our pool

Kubu, you always ask for us spread the hash. Why didn't you set up your pool in time? You had a chance, I was here at launch. You had 20 minutes before ocminer configured his pool.

i am ready. i have any problem with compille wallet. when ready i say about up. and write dev about problem. but dev not answear me

Where did you tried to contact us?

Anyway you need to install libevent-dev before compiling and create the obj/tor directory in elektron/src path.

Regards.

[Digital_Currency_LTD]

guys please spread hash on our pool

Kubu, you always ask for us spread the hash. Why didn't you set up your pool in time? You had a chance, I was here at launch. You had 20 minutes before ocminer configured his pool.

i am ready. i have any problem with compille wallet. when ready i say about up. and write dev about problem. but dev not answear me

Good night all and happy work

Good night Kubu!

[Digital_Currency_LTD]

guys please spread hash on our pool

Kubu, you always ask for us spread the hash. Why didn't you set up your pool in time? You had a chance, I was here at launch. You had 20 minutes before ocminer configured his pool.

i am ready. i have any problem with compille wallet. when ready i say about up. and write dev about problem. but dev not answear me

Where did you tried to contact us?

Anyway you need to install libevent-dev before compiling and create the obj/tor directory in elektron/src path.

Regards.

Dev you said it will be an update soon. When?

[topcat363]

Any ETA on your updates, dev?

[Digital_Currency_LTD]

Good sign....

https://twitter.com/BittrexExchange/status/588789681803763712

[ElektronFoundation]

We are proud to announce the release of Elektron with Automatic Checkpointing (ACP). Most of the coins on the market has a way of setting checkpoint completely manual. This can bring to various problems and possible issues such the needing of update and release new wallet software everytime coders set new checkpoints. Also this could lead to various malicious wallet release from hackers due to high number of updates needed to add checkpoints during the coin's life.

Automatic Checkpointing FAQ

What is checkpointing?
Checkpointing was originally built in to Bitcoin original client in order to prevent dishonest people reversing transactions and taking back the money they had sent. Imagine someone sends you money and you dispatch goods only to find that they have taken the money back out of your account.

The basic checkpointing feature in Bitcoin and its clones makes sure that the software only connects to the blockchain defined by the developers. This is a safety feature to stop malicious users from trying to force clients on to a different blockchain. The blockchain has all the coins transactions of a certain cryptocurrency written into it. Every block in the blockchain has a unique string of characters called a hash. In the client the checkpoints are defined by providing the block number and its hash, this is then compiled and distributed. Clients will only accept the blockchain that has the corresponding block number and hash defined in the code. Checkpointing offers some protection against attackers but only up to the last checkpoint. So malicious users could try to orphan blocks after the last checkpoint and reverse transactions with 51% attacks.

What is a 51% attack?
As the network is decentralised the blocks that make it into the blockchain need to be agreed upon by the majority of the miners. So if someone has 51% of the network mining power they are able to dictate which blocks get accepted. Typically a 51% attack is used to force the network to accept alternative blocks to ones that have already made it into the chain. The result of this is to make the transactions in the original blockchain disappear. Typical clients will broadcast the transaction again but the attacker will make sure that their transaction disappears. The aim of this sort of attack is typically to reverse transactions. As these attacks orphan the original blocks, pools and miners also find that the coins they mined disappear. The victims of these attacks are the recipient of the attacker's transaction and the miners whose mined coins from the original blocks will disappear.

What is Automatic Checkpointing?
AutoCheckpointing allows us to send out checkpoints without having to redistribute the Elektron software. This works by having a 'master node' which checkpoints each block it sees on the network protecting it from the attacker. This checkpoint is then picked up by all the other clients on the network which will then ignore any blocks generated by a 51% attack. This protects merchants from transaction reversal and miners from losing their newly minted coins. With AutoCheckpointing, Elektron becomes the most secure of all the Scrypt cryptographic currencies.

Why doesn't Bitcoin or Litecoin have this protection?
51% attacks have generally been theoretical and in the past they have only happened a handful of times to newly born coins. However it appears that the cryptocoin landscape is becoming increasingly hostile as people invest in larger and more expensive mining farms and have access to large mining pools. The attacks that were theoretical are now becoming commonplace to coins which do not have a large amount of hash power.

Bitcoin and Litecoin have never been subjected to successful 51% attacks as their hashpower has so far been too great for the attackers to target. It would seem that as they have not suffered from these attacks then it is not a problem for them but we believe this complacency is the biggest threat. It may be true that Bitcoin is safe for now but all crypto currencies should have some concern for this issue as hash power should never be taken for granted.


Is this an user profitable solution?
ACP is a form of securing the blcokchain that we have put in place because we believe security comes first. Attacks on this new breed of crypto currencies are on the rise with the attackers becoming more and more resourceful. We are the first X13 based coin to respond to this threat by recruiting the best minds in this domain to ensure everyone is protected even those who engage in speculative mining and to whom we owe a debt of gratitude for their patience and understanding.

How will Elektron continue to innovate to ensure security and decentralisation?
This is the hard work that needs to be done and we will continue to listen to our community and innovate on the design and implementation of the ACP. We believe that Elektron should be powered by the community and for the community.

This is a form of dev-team-trust as the checkpoint master node is deployed and maintained by the developers team. Currently no other persons but developers has access to this system but it is planned to make the checkpointing system distributed over time. Distributing this system would allow several stakeholders to have a vote on which block gets checkpointed. The controls in the system are very limited and only allow the developer to change the depth at which the blocks are checkpointed. This is an automated process and there is no facility to pick and choose which blocks get checkpointed.

We will explain how our trust system will work later on.

[tic-tac-totoro]

C-Cex still in maintenance 

[ElektronFoundation]

C-cex opened wallets.

https://twitter.com/CryptoCurrEncyX/status/588825100260143104

[tm2013]

We are proud to announce the release of Elektron with Automatic Checkpointing (ACP). Most of the coins on the market has a way of setting checkpoint completely manual. This can bring to various problems and possible issues such the needing of update and release new wallet software everytime coders set new checkpoints. Also this could lead to various malicious wallet release from hackers due to high number of updates needed to add checkpoints during the coin's life.

Automatic Checkpointing FAQ

What is checkpointing?
Checkpointing was originally built in to Bitcoin original client in order to prevent dishonest people reversing transactions and taking back the money they had sent. Imagine someone sends you money and you dispatch goods only to find that they have taken the money back out of your account.

The basic checkpointing feature in Bitcoin and its clones makes sure that the software only connects to the blockchain defined by the developers. This is a safety feature to stop malicious users from trying to force clients on to a different blockchain. The blockchain has all the coins transactions of a certain cryptocurrency written into it. Every block in the blockchain has a unique string of characters called a hash. In the client the checkpoints are defined by providing the block number and its hash, this is then compiled and distributed. Clients will only accept the blockchain that has the corresponding block number and hash defined in the code. Checkpointing offers some protection against attackers but only up to the last checkpoint. So malicious users could try to orphan blocks after the last checkpoint and reverse transactions with 51% attacks.

What is a 51% attack?
As the network is decentralised the blocks that make it into the blockchain need to be agreed upon by the majority of the miners. So if someone has 51% of the network mining power they are able to dictate which blocks get accepted. Typically a 51% attack is used to force the network to accept alternative blocks to ones that have already made it into the chain. The result of this is to make the transactions in the original blockchain disappear. Typical clients will broadcast the transaction again but the attacker will make sure that their transaction disappears. The aim of this sort of attack is typically to reverse transactions. As these attacks orphan the original blocks, pools and miners also find that the coins they mined disappear. The victims of these attacks are the recipient of the attacker's transaction and the miners whose mined coins from the original blocks will disappear.

What is Automatic Checkpointing?
AutoCheckpointing allows us to send out checkpoints without having to redistribute the Elektron software. This works by having a 'master node' which checkpoints each block it sees on the network protecting it from the attacker. This checkpoint is then picked up by all the other clients on the network which will then ignore any blocks generated by a 51% attack. This protects merchants from transaction reversal and miners from losing their newly minted coins. With AutoCheckpointing, Elektron becomes the most secure of all the Scrypt cryptographic currencies.

Why doesn't Bitcoin or Litecoin have this protection?
51% attacks have generally been theoretical and in the past they have only happened a handful of times to newly born coins. However it appears that the cryptocoin landscape is becoming increasingly hostile as people invest in larger and more expensive mining farms and have access to large mining pools. The attacks that were theoretical are now becoming commonplace to coins which do not have a large amount of hash power.

Bitcoin and Litecoin have never been subjected to successful 51% attacks as their hashpower has so far been too great for the attackers to target. It would seem that as they have not suffered from these attacks then it is not a problem for them but we believe this complacency is the biggest threat. It may be true that Bitcoin is safe for now but all crypto currencies should have some concern for this issue as hash power should never be taken for granted.


Is this an user profitable solution?
ACP is a form of securing the blcokchain that we have put in place because we believe security comes first. Attacks on this new breed of crypto currencies are on the rise with the attackers becoming more and more resourceful. We are the first X13 based coin to respond to this threat by recruiting the best minds in this domain to ensure everyone is protected even those who engage in speculative mining and to whom we owe a debt of gratitude for their patience and understanding.

How will Elektron continue to innovate to ensure security and decentralisation?
This is the hard work that needs to be done and we will continue to listen to our community and innovate on the design and implementation of the ACP. We believe that Elektron should be powered by the community and for the community.

This is a form of dev-team-trust as the checkpoint master node is deployed and maintained by the developers team. Currently no other persons but developers has access to this system but it is planned to make the checkpointing system distributed over time. Distributing this system would allow several stakeholders to have a vote on which block gets checkpointed. The controls in the system are very limited and only allow the developer to change the depth at which the blocks are checkpointed. This is an automated process and there is no facility to pick and choose which blocks get checkpointed.

We will explain how our trust system will work later on.

Good job!

[ElektronFoundation]

EKN listed on  http://www.worldcoinindex.com/coin/elektron

[ZaZ59]

Hi,

EKN is now listed on www.altcoinprofitability.com!

Plz add us in your OP, ty

Best regards

[Starin]

EKN listed on  http://www.worldcoinindex.com/coin/elektron

News on trex?

[tm2013]

EKN listed on  http://www.worldcoinindex.com/coin/elektron

News on trex?

Probably soon