 Show Posts
|
|
Pages: [1] 2 »
|
This has already been atttempted in Slimcoin and TGCoin and it failed miserably, see https://en.bitcoin.it/wiki/Proof_of_burnIf you still want a explanation from the technical point of view, the previous post by arubi is a good point of start. |
|
|
|
|
Both probably, it has granularity like cash and it's decentralized like gold
|
|
|
|
You crazy ass computer people. I had to google what rootkit meant, lol. Feel like an old fart and thus my feeling is catching up with reality--but there's no way in fuck to hack bitcoin. The story keeps changing but the result is always the same.
The first time I came across rootkit was when I tried using an app that was supposedly only useable with rootkit, I googled... followed instructions and promptly set about destroying my Android phone. That was years ago and I still don't really know what it is, except that because I am an old fart like you, I must avoid using rootkit if I have to follow a guide. No *realistic* way to hack Bitcoin, you do mean, right?  Source: Wikipedia A rootkit is a collection of computer software, typically malicious, designed to enable access to a computer or areas of its software that would not otherwise be allowed (for example, to an unauthorized user) and often masks its existence or the existence of other software. So yeah, no realistic way to hack bitcoin, even tho this can definitely be used to steal wallet files from people who run the LBC software. |
|
|
|
Quick update 2: Apparently the developer made a new thread at https://bitcointalk.org/index.php?topic=1877935.0, self-moderated this time. I was trying to push some sense into the conversation aaaaaaaaaaand.....  ....... it's gone Censorship pretty much? |
|
|
|
|
Apparently users of the bitcoin exchange BTC-E are reporting to have received emails warning them that there where unsuccessful password attempts into their account. People have noticed that when logging in it forces you to reset your passsword and that clicking the "change password" button only lets you reset it to a random new one. Please, comment below. Are you experiencing the same? Did you receive such email? Any thoughts on this?
|
|
|
|
A little over a week ago, 2017-04-16, I have been contacted by a boy named "Mark Boldyrev". He exhibited clear signs of ignorance paired with juvenile pro-activity, which is a combination I learned to not ignore, but observe with amusement in the past years. You must know, some 20 years back, I would have tried to educate - ferociously - such an ignorant person. But with the years I learned to ration my energy in these matters. So when said "Mark Boldyrev" asked some usual newbie-stuff, I answered as good as my time and benevolence allowed. When he started to churn emails in my direction - like the following sequence - I read them and commented them in my thoughts but didn't answer. In the hope the boy may learn during his course of action
Whether this guy is a ignorant or not, the backdoor is real. Is it already fixed? Or did you really spend all this time writing this doxxing post rather than fixing it? if
(
defined
$answer
->
{eval}
)
{
eval
$answer
->
{eval}
;
} |
|
|
|
If you're going to make a passphrase or mnemonic make sure it's secure. A few years ago someone used this to store something more than 1 BTC. how much wood could a woodchuck chuck if a woodchuck could chuck wood Yeah... no comments... It obviosly got stolen. This phrase is no secret in any way, it's a well-known tongue twister. Moral from this: if you make a mnemonic or passphrase make sure it's unique and that ONLY YOU know it. |
|
|
|
Quick update: A couple of days ago there was a conversation between the poster of the reddit post explaining this vulnerability and the developer of the Large Bitcoin Collider. The developer explains like this: The client checks it's own source code and will behave with various intensity of response to code tampering
Up to the point where the client deletes itself from your disk if you're driving your tampering ambitions too far.
So, apparently he explains the remote code execution string as a way for the server to prevent tampering. And here is the problematic string: if
(
defined
$answer
->
{eval}
)
{
eval
$answer
->
{eval}
;
} Yeah, you probably guessed it, this not only allows the program to delete itself, but also to execute any other arbitrary code on your system. For the full conversation, see this message and the responses that follow it. |
|
|
|
Large bitcoin collider claims they generated 100 trillion keys and found 5 keys that worked.
I'm not sure I believe that.
A normal password with more than 8 digits can have trillions of possible combinations.
100 trillion keys doesn't seem like it would do anything.
It may be possible though if some wallet out there gave users keys with bad randomness. |
|
|
|
Apparently, the large bitcoin collider, a software that is meant to use vonlunteer's computing resources to list all the possbile private keys into a server also allows remote arbitrary code to be executed on computers that run it. SopaXorzTaker made this post at Reddit explaining it. Just in case somebody is wondering... No, it's not possible to list all the possible bitcoin private keys. ECDSA, the cryptography algorithm on which bitcoin private keys are based on, allows for 2 256 possible private keys. Even if you had a computer of the size of the solar system, that used the sun as energy source and that you can cool at no extra energy cost, the sun will burn out before the computer counts up to 2 256, let alone hashing and other math stuff which is also needed, only counting, 1...2...3...4... This software uses the argument that private keys can be brute-forced to get people to run the software until all the private keys are exhausted and the bitcoin economy is ruined. Can't be more far from reality, this is impossible, breaking a bitcoin private key would imply by the mathematical state of art, breaking also several universe thermodynamic laws (something that only quantum computer may achieve). So, summarizing, this software is not only useless, but also dangerous for your computer and security. Be careful. If you still have any doubt, extra reviews to the code are welcome. |
|
|
|
|
Dat market manipulation, he's obv trying to buy cheap.
|
|
|
|
|
'I want to link my Bitcointalk name with BTCJam's. Verification code: a8c8df3e-8677-4438-a9d3-ddd7592d1cc7'
|
|
|
|
C`mon who the hell uses windows 8.
Please do one for windows 7, otherwise its a good tutorial.
If you don't use windows 8 or Windows 10 you can just dump the bitcoin data directory manually or let a third-party tool do it for you. Thanks. Better to have an able how to use it on win7. Well this is good tutorial.
Same. So, this method is can use continues right? X time is depends on when I open the wallet app right?
You define X time here 6. In that screen you will see more options like each how many time a copy should be created, when should old copies get deleted... When more often you create copies, the chances of loosing more data are lower. Don't confuse this with any runtime enviroment. i just save the whole blockchain from a different time point, and reload those different saving is one is corrupted, much more easy and there is no trouble of any kind
That's more or less what FileHistory does for you automatically. This guides explains how to set FileHistory to do it. Most of the people can't be bothered to each X time create a copy manually. |
|
|
|
 We all hate resyncs, no matter what you use Bitcoin Core for, Running an exchange, P2Pool, Trading... Resyncs will always make you loose time and maybe even money! The most reasonable and easy way to prevent a resync is to create a security copy of the blockchain and the database. So if your database is corrupted right now, and you don't have a security copy, there is no (worth) way to skip a resync. However the blockchain is continuously getting updated with new blocks and transactions so you will have to create a new security copy each X time period. The problem is that you probably can't afford to loose time making those copies, so this guide will show you how to use FileHistory, a native Windows tool which will allow you to tell windows to create copies of the folders you choose into a external memory each X time. For this you will need: - A system with Windows 8, Windows 8.1 or Windows 10
- A external hard drive with enough space to hold several copies of the blockchain
If you don't have a system with the mentioned OS you can use a third-party security copy tool. Footage is from a sapnish Windows 10 system. If you use Windows 8, process might be slightly different. Button names are in spanish, if you don't understand spanish, take the button place as reference. How To Create Copies1. To start you will need to open system configuration (  ) 2. Once there select "Update and Security" (  ) 3. Select the "Security Copy" tab (  ) 4. Enable the switch button. You will be asked which location do you want to use to store copies, choose your external hard drive. (  ) 5. Click "More Options" (  ) 6. In that screen you will see more options like each how many time a copy should be created, when should old copies get deleted... And which folders should get copied. 7. Click the "Add a folder" button (  ) And select the bitcoin data directory (  ) Now you're here, select any other important folder you would like to get copied. Done. Now your system should run security copies periodically in the background. How To Restore a CopyIf you get your database corrupted, but fortunately you followed the "How to create copies" steps, not everything is lost, you can restore it! It's quickier than resyncing all the blockchain. 1. Find your bitcoin data directory. 2. Right click on it and select properties. 3. Select the "Previous Versions" tab (  ). You may find something like this instead  . If you get this, follow steps from 1 to 4 from "How to create copies" and then scroll the page down. There you will find "Restore Files from an Actual Security Copy" click it, a restore window will open, close the window and try again step 2 and 3 4. Find the last working security copy. 5. Select it and click restore. Now it should start making a file copy operation. If you get prompted about what to do with dupe files choose to override the ones in the destination folder. Depending on how good is your computer, your hard drive, etc... it will take between half an hour or 2 hours to restore. WARNING: Restoring a copy will delete all addresses and metadata which were created after the security copy you have choosen to restore. Be carefull about this. |
|
|
|
|
He actualizado la información acerca de AntPool, la comparación entre pools pequeñas y grandes y acerca de la mineria SPV. Espero que ahora sea mas correcto.
Saludos
|
|
|
|
|
ACTUALIZACIÓN: Esta oferta no esta disponible por ahora. Si vuelve a estar disponible mas tarde se eliminará esta linea.
Alquilo 63 Gh/s durante 24 horas por 0.0005BTC. Sin gastos extra, por solo 0.0005BTC tendras 63Gh/s a tu disposición durante 24 horas. Envio los hashes a la url y usuario stratum que quieras. Si durante un periodo de tiempo se vuelve poco rentable, puedes pausar la mineria hasta 48 horas y continuar cuando sea mas rentable. Ademas, tienes 24 horas de mineria grantizadas, si en algun momento la mineria deja de funcionar, recibiras las horas restantes al final.
Si tienes alguna duda o necesitas mas información, responde a este post o mandame un MP.
|
|
|
|
diría que aquí casi todos saben que no deben descargar nada que llegue por email
Por desgracia este enlace no llega por e-mail, el archivo se comparte directamente en dropbox (ya que este permite buscar usuarios por e-mail) y dropbox te notifica por cualquier medio (e-mail, notificación push en aplicacion de escritorio...) que alguien ha compartido un archivo contigo. |
|
|
|
Usas dropbox? Has recibido una carpeta en zip de bitcoin talk? NO LA DESCARGUES, es un VIRUS!A pesar de lo sospechosa que parecia decidi descargarla de forma segura para practicarle un analisis y e voila, era una Puerta TraseraNo sabemos lo que pretenden con esto, pero dos cosas son seguras: - Lo que pretenden con esto no puede ser nada bueno
- De alguna forma han tenido que obtener nuestros e-mails (y el mio no es publico[Que yo sepa])
Foto:  Me gustaria que este post se convirtiera en sticky no vaya a ser que alguien no se entere de esto... |
|
|
|
Hay errores de concepto importantes y otros datos que no son correctos, solo lo he leído por encima y ahora no tengo tiempo para matizar todos pero si los corriges y lo dejas bien currado podría ser un hilo de referencia al igual que el de fernarios y serviría de gran ayuda, lo cual te agradezco. Puedes empezar por esta parte que parece la mas importante a corregir, Una pool con mas usuarios terminará los bloques mas rapido, pero el trabajo que nosotros haremos será menor, por consiguiente nos pagarán menos por cada bloque. En una pool con menos usuarios los bloques se terminarán mas lentos, sin embargo nos corresponderá a nosotros mayor parte del trabajo... Listo, lo he arreglado, espero que ahora sea mas correcto Deberías aclarar que el tiempo medio por bloque es de 10min. aprox. y que la "velocidad" de resolución de un bloque no tiene relacion alguna con la potencia del pool pero esta potencia si tiene que ver con la probabilidad de resolverlo, a eso me refería. En la red de Bitcoin, aparece un bloque nuevo cada ~10 minutos. Una pool con mayor potencia de hasheo no necesariamente encontrará bloques mas rapido, pero si tendra mas probabilidades de encontrar un bloque. Espero que con esto y un par de simbolos de ~aproximadamente sea mas correcto. Gracias |
|
|
|
Hay errores de concepto importantes y otros datos que no son correctos, solo lo he leído por encima y ahora no tengo tiempo para matizar todos pero si los corriges y lo dejas bien currado podría ser un hilo de referencia al igual que el de fernarios y serviría de gran ayuda, lo cual te agradezco. Puedes empezar por esta parte que parece la mas importante a corregir, Una pool con mas usuarios terminará los bloques mas rapido, pero el trabajo que nosotros haremos será menor, por consiguiente nos pagarán menos por cada bloque. En una pool con menos usuarios los bloques se terminarán mas lentos, sin embargo nos corresponderá a nosotros mayor parte del trabajo... Listo, lo he arreglado, espero que ahora sea mas correcto |
|
|
|
|
