Here it comes my idea about this issue:Miners include few transactions in blocks because more transactions equals more probability of orphaned block so lets equal all blocks: Miners should craft a block normally, so lets imagine they generate a 250KB block. Before they send it to other node they have to concatenate junk bytes (random (?)) to the block data, so all blocks are 1MB. When a node sees this block, they broadcast it and when they finish they delete this junk bytes and they only the block. Pros: - All blocks "are" 1MB in terms of relaying them. - We avoid other more tecnical mecanisms Cons: - Bitcoin QT needs some bandwith more because now all blocks are 1MB. If one day we need to rise the 1MB block limit this process will be the same but all blocks will require to be 10MB (for example). We only need to concatenate junk to them. How to perform this hard fork?Bitcoin core developers can release an update that includes this fix but only enforcing it when the blockchain reaches the block 277000 (30 days later) so we give some time for people and miners to update their software. 
|
|
|
|
Theymos, any chance you could contact Globalsign — cloudflare's CA partner— and point out we believe their relationship with cloudflare may have been used to fraudulently issue a certificate for bitcointalk.org, ask them if they did— and if they did, to please list that certificate in their CRLs?
Did anyone actually save a MITM cert? I only have a few reports of unusual behavior -- nothing too solid. Personally, I observed 108.162.197.161 proxying the traffic verbatim, without touching the cert. I dont save it, but I can assure that when bitcointalk.org was under cloudflare a valid SSL certificate was been served. |
|
|
|
|
Erase una vez, una alegre habichuela que quería pitufear en Alemania Oriental. Por ser judía se encontró con problemas de concentración, sufrió dolores. Pero, Adolfo siguió maquillándose. Bitcoin comía frijoles. Frijoles congelados baratos embrujados que emitían más deuda. La prima de riesgo no parecía Batman si pero, la duquesa radiactiva mutó pero nunca vivió expectante.
Ataulfo atajó como siempre, hacer explotar Bitcoin fue imposible durante la batalla de MtGox como otras guerras. Pero, ademas Ataulfo murió.
Su dinero desapareció hace más de 77 segundos que pudo aprovechar para correr al coche híbrido con ella, su habichuela mágica amarronada. Ella introdujo el Bitcoin por la ranura de atrás y entonces explotó nuevamente su potencia fúnebre. Zombies, cucarachas, banqueros, barqueros, políticos, habichuelas de uranio enriquecido, sucumbieron ante el nauseabundo lider amarillo limón.
Llegaron los socialistas austriacos al turrón, enfadaron al Zorro americano sofrólogo carnicero de Auschwitz. Quien disfrutó envenenar por doquier a hadas mágicas, elfos salvajes y hobbits mongólicos.
Finalmente comenzó el apocalipsis, Mt.Gox cerró temporalmente 2 segundos, pero emergió cual reptil godzilliense en carnaval. Aquello fue maravilloso. Luces apagadas, sexo Greysiano y habichuelas.
Satoshi engendró un clon robotico de supernovas amarillas voladoras perfumadas preparadas para amar e hipnotizar a suricatos plumiferos. Delfines purpuras transgénicos colonizaron Marte y minaron ASICs ultrasónicos. Entonces Nakamoto revolucionó metódicamente sus abrazos especuladores.
Batman estaba todo somnoliento por las amebas afrodisiacas afroamericanas desfogadas que casi se muere cayéndose con su lapicero oscuro, y pasó a Robin Hood vestido con tremendo maquillaje que casi parecía un payaso, por eso lo sodomizó sin control. Su alpaca Paca Garrapata, también atacó y se murio.
Obama promete espiar a todos sin discriminación mientras se toca el pene. La CIA metía el satélite nuclear dentro del monedero que Merkel escogió para minar, pero Satoshi programó con Buttercoin para obtener mantequilla suavecita y esponjosa. "¿Follamos?" dijo Nacho Nakamoto, encima de Michelle agarrándole una goma. La lengua amputada le exploró y succionó leche blanca de un orificio. Salió corroyendo, entró en barrena, salió rápidamente de aquella bola grandilocuente muy chorreante de mal de Litecoin hundido de repente a capón.
La alegre habichuela saltó un eneldo dando una pirueta y dijo:
¡Arrecia increíblemente estrafalaria moneda!
Cameron Diaz, actriz rubia voladora, subió o levitó hasta follarse un suricato vizco, causándole múltiples orgasmos. Desafortunadamente llegaron a 1000
|
|
|
|
Cito el anuncio que se ha hecho en otra seccion: Many existing translations need to be updated and new languages are welcome.
Why this is important
The future of Bitcoin is closely related to decentralization. Not just the network, but the jurisdiction of all of its users, miners and businesses. Widespread adoption increases resilience and provides incentives for countries and businesses to compete in a free market. Making sure everyone can benefit from Bitcoin is also important to create a fair and sustainable economy. Yet, most countries don't have as much information available in their own languages. Bitcoin.org can help to make a difference on this level. Bitcoin.org is one of the most visited website in the world, this is an incredible chance and opportunity for the Bitcoin community.
How to help
If you speak a language other than English, or if you know anyone who does and would want to participate, You can go to Transifex : https://www.transifex.com/projects/p/bitcoinorg/ and click to join the team for your language. You can then review / improve existing translations and translate additional texts that are still not translated. New coordinators (with a good level of experience for their respective language) would be helpful for some of these teams.
When a translation is nearly complete, I usually create an editable live preview to help translators to complete their work. A few good quality translation is always worth more than many poor quality translations. All texts need to be translated and reviewed by at least two different persons (peer-reviewed), unless perhaps if you're a professional translator. It's also always welcome to ask for questions if you are unsure about anything, this can help preventing accidental changes in the meaning of some statements.
BTW, there is also many other projects listed on this page which can be translated:
http://bitcoin.org/en/support-bitcoin
Donations / Bounties
Feel free to offer a bounty if you want to incentivize people to work on translations. You can also send some tips to this address ( 112ypbXZSUnJvbAvzMNSoxHV6uJM77LSAk ) and let me know what language you want to support the most. I'll redirect these tips at the most active contributors (I'll do my best to be fair, and also keep some tips for previous most active translators who worked for free). You're also very welcome if you want to pay a professional translator directly (here's one accepting bitcoins http://hyperwyrm.co.uk/) . With the recent rise in the price, there is probably some bit-millionaire who would like to help Bitcoin reaching new horizons?
Edit: 34 mBTC donated so far, thanks!
Some priorities
These languages really need to be updated since a while:
Spanish
Polish
Russian
Chinese (Taiwan)
Persian
Arabic
Indonesian
These languages could be added soon with some help:
Japanese
Portuguese (Brazil)
Korean Resumen:Si sabes Ingles y Español (ES) puedes ayudar a traduccir Bitcoin.org registrandote en https://www.transifex.com/projects/p/bitcoinorg/Una vez registrado unete al proyecto de traducción y empieza a traducir algunas frases. No se necesita gran nivel de ingles (algunas traducciones son sencillas) pero si que se necesita profesionalidad a la hora de escribir en Español (ortografía correcta, etc). |
|
|
|
Thanks for the info, I will contribute to the spanish one.  |
|
|
|
I know I have suggested this two times but I consider it necessary. Please enable HSTS to avoid sslstrip or a MITM replacing the http page.https://en.wikipedia.org/wiki/HTTP_Strict_Transport_SecurityWith PHP check if the page is been served in HTTP, if so redirect to HTTPS. In HTTPS set the HSTS header: header("strict-transport-security: max-age=31536000");(Example implementation in PHP). That tells the browser to only use the HTTPS versión of bitcointalk.org for a year (31536000 seconds). So, my browser will go directly to https even if I have no internet conection. |
|
|
|
Thanks theymos, you rock. Please implement also HSTS to improve https: Please enable HSTS to avoid sslstrip or a MITM replacing the http page.https://en.wikipedia.org/wiki/HTTP_Strict_Transport_SecurityWith PHP check if the page is been served in HTTP, if so redirect to HTTPS. In HTTPS set the HSTS header: header("strict-transport-security: max-age=31536000");(Example implementation in PHP). That tells the browser to only use the HTTPS versión of bitcointalk.org for a year (31536000 seconds). So, my browser will go directly to https even if I have no internet conection. Thanks. |
|
|
|
|
Android app still adds 0.0005 fee but i have configured to send normal fee (0.0001) in the website.
|
|
|
|
A disfrutar lo preminado.  Preminado es incorrecto |
|
|
|
|
Bug, when using android app (last version), it adds a fee of 0.0005 instead of 0.0001 btc.
|
|
|
|
Maybe a brute for hire pool then? For multipurpose queries. Buyer inserts a certain amount of BTC to pay for solving, and workers start chipping away.
What part of "1461501637330902918203684832716283019655932542976 possibilities" yo dont understand?  |
|
|
|
Bruteforcing 2 160... Good luck at the pool 1461501637330902918203684832716283019655932542976 possibilities  |
|
|
|
Is electrum considered the "Safe way" to do it? I know I read in the past people prefer Bitcoin-qt as you have the whole block chain, and less of a chance to get duped.
Thanks
Kosta
As I said in the post, I am not developing this, just presenting the idea to the comunity so someone may develop it. The Bitcoin Core developers have telled to me that they have no time for this so the Electrum ones may have. |
|
|
|
This idea should probably not be made available for download until HD (deterministic) wallets are used in the bootable environment.
The reason for this is that in a temporary environment (or with cheap USB storage), there's plenty of risk for new unsaved Bitcoin addresses to be destroyed at shutdown. In case you don't know this, Bitcoin-Qt for instance always create a new Bitcoin address for each payment and moves the "change" of a transaction to this address. There's at least one case of someone who lost a lot of bitcoins in that exact same situation in the past.
Deterministic wallets will be (to my knowledge) immune to this problem, as all Bitcoin addresses generated by these wallets can be re-generated later if the wallet hasn't been saved correctly or when restoring an old backup.
True, we can also change this request to "Developing Bootable Electrum Wallet". This will save us from downloading the blockchain. This way we only need a bootable cd + our wallet seed to import our wallet. |
|
|
|
Un punto clave que comenta el artículo es que la policía ya ha incautado los bitcoins y los ha vendido por euros. Pero, ¿qué pasa con los bitcoins incautados si el acusado es finalmente declarado inocente? ¿Le devolverán la misma cantidad de bitcoins? ¿Qué pasa si algunos de ellos representan smart property?
Pues si, yo ya le hice el mismo comentario a la policia en twitter cuando publicaron el articulo, no contestaron. La que se puede liar puede ser bien gorda y sobretodo si han pasado 4 o 5 años hasta que acaba el juicio. Por cierto, ¿que es Smart property? Smart property es un concepto que aun no se ha llevado a cabo (o no abiertamente), consiste en que unos bitcoins representen un contrato. Ejemplo: este bitcoin representa la propiedad de una casa, el que lo tenga es el dueño legal. |
|
|
|
|
Show Posts
