 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
2
|
Local / Italiano (Italian) / Re: La storia dietro il primo blocco (alternativo) di genesi
|
on: October 12, 2022, 01:32:20 PM
|
Appena ho del tempo creo la pagina wiki "Storia di Bitcoin". Attualmente nessuno ha la versione completa (ovvero a partire dalle origini). Comunque ho contattato un editor di CoinTelegraph e mi ha detto che provvederà personalmente a contattare il giornalista per aggiornare il pezzo. Staremo a vedere  |
|
|
|
|
3
|
Local / Italiano (Italian) / Re: La storia dietro il primo blocco (alternativo) di genesi
|
on: October 11, 2022, 08:02:39 PM
|
Scusa, ma contattali quelli di cointelegraph.
Proponi la "tua versione". Almeno metti le cose in chiaro come stanno.
Lui mi sembra un vero talento. Non credo si interessi tanto a queste quisquilie  "Talento": preferisco definirmi uno che sa cosa poter trattare  Satoshi era e rimane un talento! Sia chiaro con questo non intendo dire che non mi interessano queste quisquilie: ho provato a taggare CoinTelegraph e il giornalista su Twitter e ho provato a mandare un e-mail. Non ho idea se sia stata effettivamente letta, potrei provare ad scalare l'e-mail con uno degli editori. Per carità essere giornalisti è difficile e se non si è competenti, è facile cadere in questi tranelli. Ma almeno rispondi alle e-mail e prova a discutere, invece di ignorare ogni forma di discussione! |
|
|
|
|
5
|
Local / Italiano (Italian) / Re: La storia dietro il primo blocco (alternativo) di genesi
|
on: October 10, 2022, 04:47:26 PM
|
Non ho capito.
È ufficialmente una bufala?
O sono solo vostre elucubrazioni?
Sì, sì, è una bufala. Chissà quanto ci metteranno a correggere quelli di CoinTelegraph, ma già da moltissimo tempo si sapeva di questa repo (che per altro faceva da backup alla primissima versione dei sorgenti rilasciata da Satoshi, poi da lì è iniziato lo sviluppo vero e proprio). La primissima del codice sorgente è "nov08" composta da quattro file (ovvero la versione analizzata dal mio articolo). |
|
|
|
|
6
|
Other / Beginners & Help / Re: How hard to detect scams nowadays?
|
on: October 10, 2022, 04:21:20 PM
|
|
Look at potential red flags, check which people there are behind a project and ask yourself if they're really capable of. Potential red flags include a brand new project, mention of a "centralized" token, buzzwords ("artificial intelligence with addition of blockchain and IoT for getting richer!". Anyway most of the projects in cryptocurrencies has ZERO value, beside Bitcoin, and Monero (and a few ones). Check if the project is supported by someone or any company, check who team members are.
Lack of transparency? Scam. Lack of any documentation? Scam. Did they provide you a business model that... ? Scam naturally.
|
|
|
|
|
7
|
Bitcoin / Development & Technical Discussion / Re: Why is it empty when sending rpc via curl?
|
on: October 10, 2022, 04:14:01 PM
|
Exactly, look at HTTP status code. 401 means Unauthorized, you need to supply valid username and password to be able to use RPC interface for that node. The funny thing is that I don't know where to get them from.( IP I took from the seeds In curl, I specify any login and password, but I don’t know where to get which one is needed ( Why should you have the username/password if the node is not yours? Anyone can start a node, and can restrict the json API interface. |
|
|
|
|
9
|
Bitcoin / Development & Technical Discussion / Re: Why is it empty when sending rpc via curl?
|
on: October 10, 2022, 03:50:17 PM
|
Why is it empty when sending rpc via curl? curl --user x:x --data-binary '{"jsonrpc":"1.0","id":"curltest","method":"getrpcinfo","params":[]}' -H 'content-type:text/plain;' http://95.216.35.227:8332/
Add flag --verbose to see the actual response from the server. You're sending a wrong username or password. * Trying 95.216.35.227...
* TCP_NODELAY set
* Connected to 95.216.35.227 (95.216.35.227) port 8332 (#0)
> POST / HTTP/1.1
> Host: 95.216.35.227:8332
> User-Agent: curl/7.52.1
> Accept: */*
> content-type:text/plain;
> Content-Length: 67
>
* upload completely sent off: 67 out of 67 bytes
< HTTP/1.1 401 Unauthorized
< WWW-Authenticate: Basic realm="jsonrpc"
< Date: Mon, 10 Oct 2022 15:49:26 GMT
< Content-Length: 0
< Content-Type: text/html; charset=ISO-8859-1
<
* Curl_http_done: called premature == 0
* Connection #0 to host 95.216.35.227 left intact |
|
|
|
|
11
|
Bitcoin / Development & Technical Discussion / Re: What is the best language to write a miner in?
|
on: October 10, 2022, 03:01:36 PM
|
What is the best language to write a miner in?
If you're really expert and know what you're doing, for sure C is the most powerful programming language that allows you to think as a "machine". Assembly would be more performant but good luck not loosing your mind  For people suggesting any OOP-based language or GC-based language, you're going to waste some helpful CPU burst on checking pointers, and allocations. C is a nightmare for pointers but it can allow you to write very efficient program without too much efforts. Unfortunately you need to master pointers management and you need to carefully think about the instruction cycle (fetch, decode, execute), pipelines and much more to waste CPU burst as few as possible. I think I can understand it because I already know html/css/js/php/mysql web languages and know python/c# and for learning blockchain mining I used python for test. Yes, you might understand it without too much effort but the problem is optimizing that. |
|
|
|
|
13
|
Bitcoin / Bitcoin Technical Support / Re: Cannot obtain a lock on data directory /home/ywn/btc_data.
|
on: October 10, 2022, 01:45:44 PM
|
Identify all the Bitcoin core processes, kill those "gracely" and then follow the steps that other users indicated. Your device can not obtain a lock on the folder because another process is using it.
Simply running bitcoin-cli stop in a terminal will shut it down. No process identification necessary. Yes, another possibility. I think you should specify the custom datadir for that. By the way, if I have more than one Bitcoin node running in the same machine, using that command, which node will be stopped? The daemon which is listening on the RPC port that got the shutdown message. Lets say that you have two daemons running, A and B, and you have the bitcoin.conf of node A listening on the default ports 8332/8333, and since you can't reuse the same config file for two different nodes (they must have different address/port combos) you set node B to listen on 9332/9333 through another Bitcoin.conf or you just pass those arguments on the command line. If you don't do this then it won't be able to bind the P2P & RPC ports in the first place. - So you have a particular bitcoin-cli (possibly from another binary distribution)... - ...hooked up to a particular RPC server port... - ...that shuts down the Bitcoind daemon that spawned the RPC server on that port in the first place. Thanks for the explanation! |
|
|
|
|
14
|
Bitcoin / Bitcoin Technical Support / Re: Cannot obtain a lock on data directory /home/ywn/btc_data.
|
on: October 09, 2022, 07:55:28 PM
|
Identify all the Bitcoin core processes, kill those "gracely" and then follow the steps that other users indicated. Your device can not obtain a lock on the folder because another process is using it.
Simply running bitcoin-cli stop in a terminal will shut it down. No process identification necessary. Yes, another possibility. I think you should specify the custom datadir for that. By the way, if I have more than one Bitcoin node running in the same machine, using that command, which node will be stopped? |
|
|
|
|
15
|
Bitcoin / Development & Technical Discussion / Re: What is the best language to write a miner in?
|
on: October 09, 2022, 07:45:00 PM
|
What is the best language to write a miner in?
If you're really expert and know what you're doing, for sure C is the most powerful programming language that allows you to think as a "machine". Assembly would be more performant but good luck not loosing your mind For people suggesting any OOP-based language or GC-based language, you're going to waste some helpful CPU burst on checking pointers, and allocations. C is a nightmare for pointers but it can allow you to write very efficient program without too much efforts. Unfortunately you need to master pointers management and you need to carefully think about the instruction cycle (fetch, decode, execute), pipelines and much more to waste CPU burst as few as possible. |
|
|
|
|
16
|
Local / Italiano (Italian) / Re: La storia dietro il primo blocco (alternativo) di genesi
|
on: October 09, 2022, 05:03:10 PM
|
Cointelegraph was unable to verify the authenticity of Blasko’s claims at the time of publication. This story may be updated. L’avevo letto anche io. Ovviamente la verifica di una storia del genere non deve essere facile. Ma mi chiedevo se fosse possibile buttarsi in una cosa così assurda sputtanandosi a vita. Dovresti confrontare i vari codici sorgenti estrapolati da Sourceforge e caricati su Github. Probabilmente questa persona un po' inconsciamente ha detto di aver fatto la scoperta del secolo e un editore di CoinTelegraph gli ha dato seguito. |
|
|
|
|
17
|
Bitcoin / Bitcoin Technical Support / Re: Cannot obtain a lock on data directory /home/ywn/btc_data.
|
on: October 09, 2022, 04:27:49 PM
|
-------------------------------------------------------------------------------------------------------------------------------
ywn@ywn-virtual-machine:~/bitcoin/bin$ bitcoind -connect="18.214.92.184"
Error: Cannot obtain a lock on data directory /home/ywn/btc_data. Bitcoin Core is probably already running.
ywn@ywn-virtual-machine:~/bitcoin/bin$
------------------------------------------------------------------------------------------------------------------------------
Identify all the Bitcoin core processes, kill those "gracely" and then follow the steps that other users indicated. Your device can not obtain a lock on the folder because another process is using it. |
|
|
|
|
18
|
Local / Italiano (Italian) / Re: La storia dietro il primo blocco (alternativo) di genesi
|
on: October 09, 2022, 03:54:45 PM
|
Non ha senso molto senso, il codice di Bitcoin v0.1 è noto da tempo :/ Provo a contattare l'autore dell'articolo per vedere se posso ribaltare la situazione in mio favore é il tuo momento di sbugiardarlo, allora! Lui dice che questo particolare codice è ancora precedente. Dal post di Facebook: https://www.facebook.com/jim.blaskoTo those of you that are hardcore cryptoheads like me, this is quite a cool discovery as it has all of Satoshi's personal notations in the code, and hasn't been changed by anyone this early. Sure other v0.1's exist on github but I didn't find one posted previous to 2016. I know this to be the cleanest original version of Bitcoin!
Cointelegraph was unable to verify the authenticity of Blasko’s claims at the time of publication. This story may be updated. |
|
|
|
|
20
|
Local / Italiano (Italian) / Re: La storia dietro il primo blocco (alternativo) di genesi
|
on: October 08, 2022, 04:52:58 PM
|
Me lo immagino Satoshi che un bel giorno ha l'idea di portare il poker anche su Bitcoin. Un gioco del genere comunque sarebbe stato abbastanza carino da sviluppare So che qualcuno ha sviluppato il Poker su Lightning Network, quindi non era casuale, ma una citazione di questa prima implementazione di Satoshi? Oppure è casuale ed è solo perché il gioco d'azzardo ben si combina con le caratteristiche precipue del LN? Non è facile rispondere alla domanda, al 80% direi di no. A momenti nessuno si ricorda di questi pezzi di storia di Bitcoin perché episodi di questo genere sono veramente "nascosti". Il gioco d'azzardo si combina benissimo con le caratteristiche del LN, anche se non è detta l'ultima parola Magari volevano fare un tributo a Satoshi |
|
|
|
|
You should not have exposed your IP to internet
