Bitcoin Forum
December 14, 2019, 08:02:38 AM *
News: Latest Bitcoin Core release: [Torrent]
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 »
1  Local / Actualité et News / Collision SHA1 aka "SELL SELL SELL" on: February 23, 2017, 02:57:41 PM
Première collision SHA1 aujourd'hui:
Ca rajeunit pas...

Panic sell parce que "collision SHA1" = "SHA1 est cassé, HELP!", et parce que "Bitcoin utilise SHA256, SHA c'est SHA donc Bitcoin est cassé!!1!" ?

SHA hash algorithm is broken: is Bitcoin doomed?

Par ailleurs l'adresse destinée à récompenser une collision SHA1 a du coup été vidée:
2  Local / Le Bitcoin et la loi / BNP Paribas, virement Bitstamp, et questionnaire étrange on: January 13, 2017, 11:46:15 PM
Bonjour à tous
Moi qui n'avais jamais mis les pieds sur une plateforme d'échange, j'aurais peut-être dû continuer sur ma lancée

Les faits:
  • Je me connecte comme toutes les semaines sur mon compte en ligne BNP
  • J'enregistre le compte SEPA de Bitstamp, le site me dit que je vais recevoir un code de confirmation par SMS
  • Je le reçois dans les 10 secondes et le rentre
  • Boum, je suis déconnecté
  • Je me reconnecte, et là, je tombe sur un formulaire où on me demande ma situation personnelle, ma situation professionnelle, mon patrimoine et un autre truc que j'ai oublié
  • Observateur, je trouve la case "je remplirai plus tard" malgré sa taille micrométrique et sa couleur gris très clair sur fond gris clair
  • Je coche, je valide
  • Et là, je suis redirigé vers une page de FAQ qui me dit tranquille que "l'absence d'actualisation peut contraindre BNP Paribas à mettre un terme à la relation bancaire" (article L.561-8 du code monétaire et financier)
  • En bas de page deux boutons, "Plus tard" et "Mettre à jour"

Du coup je suis en quête d'avis.
Je suis parano et c'est pas lié à mon ajout de Bitstamp?
Je risque vraiment une radiation de ma banque ?
Pourquoi ils veulent ma situation professionnelle et mon patrimoine ?
Il vaut mieux que je remplisse ces questionnaires j'imagine ?
3  Other / Meta / Phishing link on: September 16, 2014, 04:30:34 PM

Reported by Schnudelu, here:

Can we see the banhammer working?

4  Alternate cryptocurrencies / Altcoin Discussion / New and slow altcoin? on: September 12, 2014, 08:04:25 AM
In order to try a project I'd like to know which altcoins are recent and have a long block creation time (ie small number of blocks per day)
5  Other / New forum software / [Feature request] Add own JavaScript scripts on: September 09, 2014, 04:25:17 PM
I know that could be dangerous for newbies but it's much more practical than using Greasemonkey, moreover for phones/tablets.
It's nearly nothing to implement but is a great feature.

If you really think rogue scripts are really an issue the setting could be put in an hidden place, only js files from github/pastebin/etc could be used, js files must be pre-approved, etc.
6  Other / Meta / Locking the "Hal" account on: August 29, 2014, 07:30:39 AM
Now that we learnt the sad news, don't you think his account should be locked?
7  Local / Actualité et News / Décès de Hal Finney on: August 29, 2014, 07:23:42 AM
Hal Finney est mort hier soir, 5 ans après avoir appris qu'il était atteint de SLA (sclérose latérale amyotrophique, ce dont est atteint le scientifique Stephen Hawking).
En deux mots: on lui doit PGP (avec Zimmerman), il a créé le premier système proof-of-work, il est un des candidats potentiels pour la personne de Satoshi et en tout cas il est le bénéficiaire de la première transaction Bitcoin (envoyé par ce dernier).
Bref, un tas de contributions à nos vies.

Le thread "Bitcoin and me (Hal Finney)"
Pour plus de détails, Google.
8  Local / Discussions générales et utilisation du Bitcoin / Reportage France 2 du 10/01/14 on: January 10, 2014, 07:44:28 PM
Quelqu'un a regardé ? C'était bien ?
9  Other / Meta / Off-topic/troll/etc Oldminer on: January 10, 2014, 02:19:50 PM
I'm not sure the behavior of Oldminer is reportable...
Is it? For what? Trolling? Off-topic?
10  Other / Meta / List of reported threads on: January 04, 2014, 09:49:22 AM
I know some moderators think it's not a good idea to make the reports "result" (accepted or not + reason) accessible by the reporter
But would it be possible to at least show the list of the posts one reported? It shouldn't be too hard to do?
11  Other / Off-topic / Schumacher's accident on: December 30, 2013, 12:08:21 PM
No thread for Schumi?
Let me fix this

Good luck to you and your family
12  Other / Meta / Serial spammer on: December 28, 2013, 07:03:56 PM

Was coinseeker banned for spamming? Roll Eyes
13  Other / Off-topic / How to pronounce 'theymos'? on: November 29, 2013, 06:53:22 PM
Like in 'Thames' or like in 'they'?
14  Other / Meta / Bitcoratio on: November 07, 2013, 08:50:00 AM
Please put "bitcoratio" in the forbidden words list or forbid links to
This shit is regularly spammed here

▌฿ ▌Bitcoin fundation memeber|| 5Bitcoin+ free 0.4bitcoin($585) no fee,send in a minutes- accept paypal and okpay.{selling worldwide}
2 Bitcoin + free 0.1bitcoin($219) [ http://www.bitc ]
10 Bitcoin+1bitcoin($1127)
50 bitcoin + free 5bitcoin=$3999 [ http://www.bitco ]
100 bitcoin + free 11bitcoin=$6999 aims to be the world’s most trusted and used Bitcoin shop,  [ http://www.bitcorat ]
[ http://www.bitcora ]
accept paypal and okpay.
[ http://www.bitcora ]
15  Other / Meta / BitcoinTalk++ flags on: October 28, 2013, 08:52:54 PM
I'd like to use this thread to give flags to people
The flags can be positive or negative and anybody can propose someone to be flagged directly in this thread

Currently, the two people with the most reports ( are candoo and usamakhalid961 so I'd like to start with them
Candoo is accused of scamming attempt and usamakhalid961 of spamming
Please give me your thoughts
16  Other / Meta / List of our bad reports on: September 25, 2013, 05:37:03 PM
Could we have access to the bad reports we made?
This would allow us to know what we think is reportable but is not
Or PM us to explain why the report is bad
17  Bitcoin / Wallet software / Let's bring some centralisation on: September 20, 2013, 08:47:13 AM
One Bitcointalk "ad" states the following:
Creating a Bitcoin client that fully implements the network protocol is extremely difficult. Bitcoin-Qt is the only known safe implementation of a full node. Some other projects attempt to compete, but it is not recommended to use such software for anything serious. (Lightweight clients like Electrum and MultiBit are OK.)
Am I the only one seeing a conflict of interests here?
Isn't bitcoin-qt the only known safe implementation of a full node because it's buggy and people can't rightly reproduce its bugs behaviour?
18  Bitcoin / Development & Technical Discussion / Forced rescan on: September 15, 2013, 04:24:11 PM
Could bitcoin-qt devs implement a forced rescan triggered by a key inside the wallet.dat?
This would be useful when third party tools add or remove addresses from it
19  Economy / Services / [Graphic designer needed] Four Horsemen of the Infocalypse on: September 15, 2013, 11:14:31 AM
I think it would be great to have some pretty images of the Four Horsemen of the Infocalypse

Something like this:

But using a decent "Four Horsemen of the Apocalypse" as a starting image, like this one:

But others are nice too:

It's not a paid request, it would be a gift to the bitcoin/internet community
I hope some of you will be interested
20  Bitcoin / Development & Technical Discussion / New Pywallet 0.0.1a6 on: September 15, 2013, 12:19:58 AM
Pywallet is a software I forked 2 years ago. It allowed importing addresses into wallets and dumping wallets. Since then I added functionalities like deleting keys, merging wallets and building transactions, among others.
I have planned to rebuild Pywallet from scratch for a few months now.

Some reasons made this rebuilding absolutely necessary:
  • I'm far better at Python and Bitcoin
  • The amount of code I added is huge and the additions lacked logic
  • The code then became a mess and hard to maintain
  • This prevents developpers to read/check the code efficiently
  • A part of the code is from Joric and this prevents me from having a global view of the code
  • The CLI and the WUI of pywallet are totally divided, so:
    • The features that are shared by them are written twice
    • They don't even have access to the same features
  • Some dependencies are actually unnecessary
  • I'd like to have a GUI

The rebuilding has now started.
Currently the plan is:
  • Create unique feature declarations
  • Create the CLI system and make it handle the features
  • Create the GUI system and make it handle the features
  • Create the WUI system and make it handle the features
  • Easy update
  • Windows executable (only one file)
  • Make walletdump reads a passphrase
  • Implement real features*
  • Make a CSS for the WUI
  • Use Ajax in the WUI
  • Create a class instead of using global variables

The purpose of this thread is to post the progression and to read about the suggestions or comments you might have.

* Implemented features so far:
Dump your wallet
Dump your keys

Dump your transactions to a file **
Recover wallets
Import a key into your wallet
Import keys

Merge two wallets
Import a transaction into your wallet
Import a read-only address (encrypted wallets only)
Get some info about one key and sign/verify messages
Print the balance of a Bitcoin address

Delete keys from your wallet
Transaction creation
Plus those new ones:
ECDSA calculations
Dump wallets from other clients ** (Electrum, other)

** Not sure I will ever implement it

Signed files checksums (signed with 1Azzay7wH1FnDE5yZMPU57y75SuT4DbGc7):
  MD5           3ebe9b641bc3511e366fa9dc868bdbef
  SHA1          bfd521ecc8364e292b1d4e7fabccfdd93c77b9c2
  SHA256        0fe5c2b8878196d1f2d3626c35b0e9f39a233e658304c9f2162aa8aad07e8a16
  SHA512        803892c90cf3b02640110d370f3fe7c1eb5fa57d943d10439e8e78b617261c38
  MD5           0ff99e98d5a07fddf7e7d20bce01aa63
  SHA1          01293db30497fd139e2e9415a076977ecd2b98ce
  SHA256        4da78b463b067bef501051d4f51f027c479e8706657d630273febd2576dbd288
  SHA512        5e84110cda8c51077313c00e204b52a9d2bc56053f3b618481a2fdba22f10bc5
  MD5           464060d5ac6a702390182deb0d12ab27
  SHA1          52eb984f273975daf1173554e81c77bdcbb1add1
  SHA256        cbd79d59112d9180e2f3f2d8fb631d9a1b36dc4a0207fa3f39832325697606ed
  SHA512        a698f94fa2bb7303bc05f5f5bea5f9f43db0b3b84cb28020115ff9ef18f82e96
  MD5           52e0895e4c8da43b9a78909e7772c18d
  SHA1          5bae63fe5e4827d03104b76b0b673a5900be1c1b
  SHA256        9aa688140cd6c79408d5edc59ec8f2720a063771dd77b49a59e4d0cae08ef971
  SHA512        ab1b3c72c3f66b6b4696652382fe295f423d2a714f4cccecddffa60661034610
  MD5           8090c5fdb2800534c52ba24dec327b95
  SHA1          92592acc16752ea285617ff82818eea63ea99269
  SHA256        a7f6fe3398aec3075a228a1b9eca13246011bd4410acc9c26acac62ee7fda55e
  SHA512        599bc210abeaeee5a431bba29c018937f11e573c7d070d6e4a2574b9428a989f

d14d53f3231326bba42678f73e852176        NPW_0.0.1a4

If you think one file contains a malware:
  • Tell me
  • Ask mods to remove the links pointing to it (see the message I signed below)
  • Post a link to a analysis

- doesn't need pywallet to run
- more info about private key
- CLI if bad --ui
Pages: [1] 2 3 4 5 6 7 8 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!