Let me clarify: YOU CANNOT CLONE, COPY OR REPLICATE YOUR BTC. I came across this article and I found it to vbe very funny, so I posted this up so that everyone can have a good laugh.
Quote
Short story on the begining
Some time ago I learned about a huge cryptographic project, called Bitcoin. I was glad and I started to learn the theoretical side of BTC. I was really motivated by the fact that Bitcoin is a currency, which makes the users independent from the bank agents. It is an excellent solution in such poor countries like India. The idea of Bitcoin and its mathematical background are outstanding. I learned every single element of the theory with curiosity. I started to put this knowledge into practice and use this currency practically, while receiving small sums in BTC for my Mathematics private lessons from students coming from different parts of India.
It led me to discover one phenomenon by chance. I was waiting for a new BTC sum to appear, it was about 0.011 for solving a small list of mathematical equations. I obtained the information that the money transfer has already been done. I checked my BTC address using blockchain.info service to confirm the transfer. However, I was not logged in my Bitcoin Wallet. Blockchain.info still showed the old balance, which was about 0.021 BTC. Two days later I logged in my Bitcoin Wallet and I found out that the transfer was registered at the moment of sending money by the client! I was very astonished as it turned out that blockchain.info shows every single, even the tiniest transaction, and it is impossible to fake it. I decided to check what was the factor responsible for such a situation.
Explanation of BTC CLONE phenomenon
Without mentioning technical and mathematical details, which are very complicated, I am going to describe only a general mechanism of this error. It occurred that a slight inadequacy within the process of information propagation concerning the transfer caused this effect. It is a complex mechanism, which was probably to some extent not properly implemented. In a nutshell, it is based on �convincing� particular elements of the BTC network that the transaction has been done through common to the sender and the receiver of the transfer information for subsequent elements of the BTC network about the value of transfer. However, there is such a moment in the system of subsequent transfer confirmations, where chargebacks with the same sum can be done and it results in two contrary pieces of information in �the system of confirmations�. The most important is that for each one Bitcoin Wallet address it would be a slightly different moment. It is hard to explain the reason of such a situation, but it is connected with the type of the server, where the blocks update takes place. I will describe it more precisely while having my calculations finished. Another important information is that only the part of �feedback confirmations� would work properly (it is complicated as well).
THIS IS IMPORTANT - WORKING SOLUTION:
What is the end result? In both wallets the same BTC sums are present at the same time � in the wallet of the receiver, there is a full amount sent and in the wallet of the sender, there is a return of a part of the sum sent. Practically it can be described as:
The two BTC Wallets are needed: the sender wallet (wallet A) and the receiver wallet (wallet B).
It should be estimated (checked in the table) in which moment (precise amount of confirmations for a particular address) the chargeback should be done.
Being ready, we transfer X BTC sum from the wallet A to the wallet B.
We check the number of confirmations using blockchain.info.
Once there is an appropriate number of confirmations, the chargeback of the same sum should be done immediately (not sooner or later) from the wallet B to the wallet A.
While having done all the operation correctly, we should have X BTC in the wallet B and a part of these X BTC, usually from 0.01% to 30%. It is strictly dependent on the amount transferred and the number of confirmations. Technical details are very complicated. The number of replicated BTC increases logarithmically in relation to the amount transferred and the number of confirmations, and in a perfect situation one would transfer all the chargebacked BTC and double their amount (it is impossible to replicate 100% of BTC).
In a nutshell: the bigger amount you transfer between your two wallets, the bigger amount you replicate. Of course, those BTC replicated through chargeback are really the true BTC, and can be transferred on and will not disappear. We can make use of them.
Here are the scopes of how much we obtain transferring the amount X (from A to B) and permanently replicating it through a chargeback (from B to A):
0.0001 BTC gives from 0.000001 to 0.000013 BTC of the revenue
0.001 BTC gives from 0.00001 to 0.00015 BTC of the revenue
0.01 BTC gives from 0.0002 to 0.0019 BTC of the revenue
0.1 BTC gives from 0.003 to 0.02 BTC of the revenue
1 BTC gives from 0.05 to 0.21 BTC of the revenue
10 BTC gives from 0.3 to 2.5 BTC of the revenue
Probably (not calculated yet):
100 BTC gives from 5 to 27 BTC of the revenue
1000 BTC gives from 70 to 320 BTC of the revenue
The amount of BTC in a particular scope (from to) depends on a particular wallet address and some aspects of its synchronization with the BTC network.
To estimate the moment (precise amount of confirmations for a particular address), where �the chargeback� from the wallet A to the wallet B should be done, I created a small script-calculator. (calculator.exe), where you indicate your A and B addresses and this script-calculator counts your confirmations. It is made for Windows operating system, because I have no other systems at school. I am really sorry, but I cannot write it on a website as I do not know PHP. If it does not work properly on other Windows operating systems (we have Windows XP), I counted several million of BTC wallet addresses and put it into a table. You can search for your wallet address in the table and check the number of confirmations (available soon, i need to check integrity and correctness of data)
If the cloning does not work properly, the test should be done taking into consideration other value estimated with the calculator. For instance, the calculator indicates the value 16 for your address, but the cloning is not successful, so you should try with 15 or 17. Remember, it is an experimental method, which requires more research.
I am not a wealthy Mathematics teacher. My monthly salary allow me to buy only 0.37 BTC today. After paying the bills, buying food for children and family there is nothing left for the above mentioned experiments and BTC replication operations.
If you enrich yourself a little bit thanks to this description, you can donate a small sum of BTCs to my address: 19fTAqRbUYUjwsJpM9ApCsddxgJqEaWG2U. While having an appropriate sum, I could be able to profit from the discovery described above.
Thank you for your attention. Any question you can send to: [email protected]. I am eager to help if only I am able to. I check my e-mail twice or three times a week.
Some time ago I learned about a huge cryptographic project, called Bitcoin. I was glad and I started to learn the theoretical side of BTC. I was really motivated by the fact that Bitcoin is a currency, which makes the users independent from the bank agents. It is an excellent solution in such poor countries like India. The idea of Bitcoin and its mathematical background are outstanding. I learned every single element of the theory with curiosity. I started to put this knowledge into practice and use this currency practically, while receiving small sums in BTC for my Mathematics private lessons from students coming from different parts of India.
It led me to discover one phenomenon by chance. I was waiting for a new BTC sum to appear, it was about 0.011 for solving a small list of mathematical equations. I obtained the information that the money transfer has already been done. I checked my BTC address using blockchain.info service to confirm the transfer. However, I was not logged in my Bitcoin Wallet. Blockchain.info still showed the old balance, which was about 0.021 BTC. Two days later I logged in my Bitcoin Wallet and I found out that the transfer was registered at the moment of sending money by the client! I was very astonished as it turned out that blockchain.info shows every single, even the tiniest transaction, and it is impossible to fake it. I decided to check what was the factor responsible for such a situation.
Explanation of BTC CLONE phenomenon
Without mentioning technical and mathematical details, which are very complicated, I am going to describe only a general mechanism of this error. It occurred that a slight inadequacy within the process of information propagation concerning the transfer caused this effect. It is a complex mechanism, which was probably to some extent not properly implemented. In a nutshell, it is based on �convincing� particular elements of the BTC network that the transaction has been done through common to the sender and the receiver of the transfer information for subsequent elements of the BTC network about the value of transfer. However, there is such a moment in the system of subsequent transfer confirmations, where chargebacks with the same sum can be done and it results in two contrary pieces of information in �the system of confirmations�. The most important is that for each one Bitcoin Wallet address it would be a slightly different moment. It is hard to explain the reason of such a situation, but it is connected with the type of the server, where the blocks update takes place. I will describe it more precisely while having my calculations finished. Another important information is that only the part of �feedback confirmations� would work properly (it is complicated as well).
THIS IS IMPORTANT - WORKING SOLUTION:
What is the end result? In both wallets the same BTC sums are present at the same time � in the wallet of the receiver, there is a full amount sent and in the wallet of the sender, there is a return of a part of the sum sent. Practically it can be described as:
The two BTC Wallets are needed: the sender wallet (wallet A) and the receiver wallet (wallet B).
It should be estimated (checked in the table) in which moment (precise amount of confirmations for a particular address) the chargeback should be done.
Being ready, we transfer X BTC sum from the wallet A to the wallet B.
We check the number of confirmations using blockchain.info.
Once there is an appropriate number of confirmations, the chargeback of the same sum should be done immediately (not sooner or later) from the wallet B to the wallet A.
While having done all the operation correctly, we should have X BTC in the wallet B and a part of these X BTC, usually from 0.01% to 30%. It is strictly dependent on the amount transferred and the number of confirmations. Technical details are very complicated. The number of replicated BTC increases logarithmically in relation to the amount transferred and the number of confirmations, and in a perfect situation one would transfer all the chargebacked BTC and double their amount (it is impossible to replicate 100% of BTC).
In a nutshell: the bigger amount you transfer between your two wallets, the bigger amount you replicate. Of course, those BTC replicated through chargeback are really the true BTC, and can be transferred on and will not disappear. We can make use of them.
Here are the scopes of how much we obtain transferring the amount X (from A to B) and permanently replicating it through a chargeback (from B to A):
0.0001 BTC gives from 0.000001 to 0.000013 BTC of the revenue
0.001 BTC gives from 0.00001 to 0.00015 BTC of the revenue
0.01 BTC gives from 0.0002 to 0.0019 BTC of the revenue
0.1 BTC gives from 0.003 to 0.02 BTC of the revenue
1 BTC gives from 0.05 to 0.21 BTC of the revenue
10 BTC gives from 0.3 to 2.5 BTC of the revenue
Probably (not calculated yet):
100 BTC gives from 5 to 27 BTC of the revenue
1000 BTC gives from 70 to 320 BTC of the revenue
The amount of BTC in a particular scope (from to) depends on a particular wallet address and some aspects of its synchronization with the BTC network.
To estimate the moment (precise amount of confirmations for a particular address), where �the chargeback� from the wallet A to the wallet B should be done, I created a small script-calculator. (calculator.exe), where you indicate your A and B addresses and this script-calculator counts your confirmations. It is made for Windows operating system, because I have no other systems at school. I am really sorry, but I cannot write it on a website as I do not know PHP. If it does not work properly on other Windows operating systems (we have Windows XP), I counted several million of BTC wallet addresses and put it into a table. You can search for your wallet address in the table and check the number of confirmations (available soon, i need to check integrity and correctness of data)
If the cloning does not work properly, the test should be done taking into consideration other value estimated with the calculator. For instance, the calculator indicates the value 16 for your address, but the cloning is not successful, so you should try with 15 or 17. Remember, it is an experimental method, which requires more research.
I am not a wealthy Mathematics teacher. My monthly salary allow me to buy only 0.37 BTC today. After paying the bills, buying food for children and family there is nothing left for the above mentioned experiments and BTC replication operations.
If you enrich yourself a little bit thanks to this description, you can donate a small sum of BTCs to my address: 19fTAqRbUYUjwsJpM9ApCsddxgJqEaWG2U. While having an appropriate sum, I could be able to profit from the discovery described above.
Thank you for your attention. Any question you can send to: [email protected]. I am eager to help if only I am able to. I check my e-mail twice or three times a week.
Link to Original Article:
http://www.sharma.binhoster.com/