|
In generale il file wallet di Bitcoin si trova qua su windows:
%appdata%\Bitcoin
( scrivilo nella barra indirizzi )
Prima di eventuali aggiornamenti fai sempre una copia di backup.
Aggiornando ad alcune versioni successive di Bitcoin il wallet potrebbe non essere più compatibile con quelle vecchie.
( quindi in caso di problemi potrebbe esserti necessario reinstallare una vecchia versione di Bitcoin )
|
|
|
|
I think that archive.org is a very good example  |
|
|
|
|
I think that it's already possible to use Bitcoin URI with online wallet.
Gmail already support "mailto:", so I think that it's possible to do the same with Blockchain.info/wallet ( example )
|
|
|
|
|
Can you add support for Bitcoin URI?
|
|
|
|
My suggestion to you is to give an offer directly to Ogrr. ( maybe you can make some money ... ) They haven't automatic funds right now, they always need an admin that gives you a new address, and to confirm the transaction  I think that they are using Phpbb. After that ( if they accept your offer ), you will probably learn more about the phpbb board. |
|
|
|
|
Any news about "automatic funds" ?
how long is required an administrator to deposit/withdraw bitcoins?
|
|
|
|
The main difference is that with Bitcoin we will be able to exchange between every forums/communities!  I really think that releasing mods for the most common boards ( phpbb, smf, invision, vbulletin ... ) will give an huge increase to the Bitcoin diffusion/circulation/propagation ... instantly! There are many mods for all these boards available. ( they just create and use an "internal virtual currency" ) We just need that someone starts to modify them to support Bitcoin. |
|
|
|
It seems free between users that use the app. Anyway, as he said it's in beta ... It's better if you show more love and suggestions  |
|
|
|
|
- 1 bill : 1 account
No one can add more than 1 time a bill to an account
- The reward for the first account ( the first one that signed/entered the bill ) comes only after "another account" has entered the bill
The bill must pass from hand by hand.
- The reward for the first account must be higher than rewards for next accounts, example with the same bill:
first account - 0.01 ( only after another account entered it )
second account - 0.0001 ( and the first account will the "the reward" 0.01 )
second account - 0.0000 ( the user tried to enter again the bill )
third account - 0.0001 ( first account will also get 0.0001, or 0.00001 ... )
( these are just examples, you should find the better values to make it working good )
- There must be a limit to withdraw bitcoin from an account, example: 0.1 Bitcoin
|
|
|
|
|
How many confirmations do you wait?
|
|
|
|
|
Non importa la tassa iniziale, potresti comunque ritirare ogni successivo pagamento.
L'altro problema è che comunque paypal non è amichevole su queste transazioni, magari potresti finire nei casini il mese prossimo ( per conto tuo, per colpa di qualcun'altro ... ) ... e paypal andrebbe magari ad annullare tutte le ultime transazioni sospette. E quindi anche di chi magari farebbe affari con te nei prossimi 2/3 giorni tanto per dire.
Al di la della tua buona fede ( che comunque dovresti dimostrare in qualche modo, e 2 euro non sono buon modo )
Nulla di personale, ma paypal rimane sempre un metodo ad alto rischio.
Altri metodi potrebbero essere quelli di ricaricare la postepay di qualcuno, via contanti, alle poste. ( vedi se trovi qualcuno )
|
|
|
|
Another idea - allow people to donate directly to the balance of all bills. So, say someone wanted to help the Bitcoin cause, and donated 1 BTC. And say there had been 500 bills entered (and presumably written upon) up to that point. Then each bill would have 0.002 BTC added to the balance of it. He can also add a "score", so there will be "the best donors score"  It'd be a good way to sort of automatically keep at least some BTC on each of the bills for anyone who wants to help out. And maybe, if a bill isn't entered again within a year, you could mark it as "destroyed" and assume that it is no longer in circulation, moving those coins to other newly entered bills. Good ideas I am still interested in hearing more about your incentive to people who first enter bills. I think it'd be great if the incentive was only realized once the bill was entered a second (third, fourth, etc) time by someone else.
Yes, all the system aims to incentive people to enter bills, there must be some good rules to make it working good. |
|
|
|
Ho trovato questo che potrebbe essere interessante: http://shelltor.comNei pagamenti è possibile anche scegliere il servizio gratuito, vedete voi |
|
|
|
Versione intermedia fixa-bug prima della v0.6 Bitcoin version 0.5.3 is now available for download at: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/This is a bugfix-only release based on 0.5.1. It also includes a few protocol updates. Please report bugs using the issue tracker at github: https://github.com/bitcoin/bitcoin/issuesStable source code is hosted at Gitorious: http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.3#.tar.gzPROTOCOL UPDATES- BIP 30: Introduce a new network rule: "a block is not valid if it contains a transaction whose hash already exists in the block chain, unless all that transaction's outputs were already spent before said block" beginning on March 15, 2012, 00:00 UTC.
- On testnet, allow mining of min-difficulty blocks if 20 minutes have gone by without mining a regular-difficulty block. This is to make testing Bitcoin easier, and will not affect normal mode.
BUG FIXES- Limit the number of orphan transactions stored in memory, to prevent a potential denial-of-service attack by flooding orphan transactions. Also never store invalid transactions at all.
- Fix possible buffer overflow on systems with very long application data paths. This is not exploitable.
- Resolved multiple bugs preventing long-term unlocking of encrypted wallets
(issue #922). - Only send local IP in "version" messages if it is globally routable (ie, not private), and try to get such an IP from UPnP if applicable.
- Reannounce UPnP port forwards every 20 minutes, to workaround routers expiring old entries, and allow the -upnp option to override any stored setting.
- Skip splash screen when -min is used, and fix Minimize to Tray function.
- Do not blank "label" in Bitcoin-Qt "Send" tab, if the user has already entered something.
- Correct various labels and messages.
- Various memory leaks and potential null pointer deferences have been fixed.
- Handle invalid Bitcoin URIs using "bitcoin://" instead of "bitcoin:".
- Several shutdown issues have been fixed.
- Revert to "global progress indication", as starting from zero every time was considered too confusing for many users.
- Check that keys stored in the wallet are valid at startup, and if not, report corruption.
- Enable accessible widgets on Windows, so that people with screen readers such as NVDA can make sense of it.
- Various build fixes.
- If no password is specified to bitcoind, recommend a secure password.
- Automatically focus and scroll to new "Send coins" entries in Bitcoin-Qt.
- Show a message box for --help on Windows, for Bitcoin-Qt.
- Add missing "About Qt" menu option to show built-in Qt About dialog.
- Don't show "-daemon" as an option for Bitcoin-Qt, since it isn't available.
- Update hard-coded fallback seed nodes, choosing recent ones with long uptime and versions at least 0.4.0.
- Add checkpoint at block 168,000.
Thanks to everybody who contributed code or helped test this release: Pieter Wuille Luke Dashjr Wladimir J. van der Laan Gavin Andresen Matt Corallo Lars Rasmusson Janne Pulkkinen Gregory Maxwell Daniel Folkinshteyn Chris Moore |
|
|
|
@edd Great! You did an awesome work! Do you think that you will be able to support for other currencies? ( euro, gbp ... ) |
|
|
|
|
Show Posts
