Jump to content

Community durchsuchen

Zeige Ergebnisse für die Stichwörter "'bitcoin core'".

  • Suche mithilfe von Stichwörtern

    Trenne mehrere Stichwörter mit Kommata voneinander
  • Suche Inhalte eines Autors

Inhaltstyp


Forum

  • Bitcoins
    • Allgemeine Diskussionen
    • Presse
    • Technik, Entwicklung & Sicherheit
    • Mining
    • Recht und Steuern
  • Altcoins
    • Allgemeine Diskussionen
    • Mining
    • Börsen & Handelsplätze
  • Wirtschaft
    • Wirtschaftliche Bedeutung
    • Kursentwicklung & Chartanalyse
    • Akzeptanzstellen
    • Diskussionen zum Handel
    • Projektentwicklung
    • Service-Diskussion
    • Kleinanzeigen
  • Börsen & Handelsplätze
    • Allgemeine Diskussionen
    • Bitcoin.de (mit Support)
    • Bitstamp
    • BTC-E
    • Kraken
    • LocalBitcoins
    • Bitcoin-Central
    • weitere Börsen
    • Geldtransfer-Systeme
  • Andere Sprachen / Other languages
    • Englisch / English
    • Französisch / Français
    • Spanisch / Español
    • Italienisch / Italiano
    • Polnisch / Polski
  • Sonstiges
    • Forum über das Forum
    • Offtopic

Finde Suchtreffer ...

Suchtreffer enthalten ...


Erstellungsdatum

  • Beginn

    Ende


Zuletzt aktualisiert

  • Beginn

    Ende


Suchtreffer filtern nach ...

Benutzer seit

  • Beginn

    Ende


Gruppe


AIM


MSN


Webseite


ICQ


Yahoo


Jabber


Skype


Wohnort


Biografie


Interessen


Beruf

10 Ergebnisse gefunden

  1. Hallo, auf meinem Bitcoin Core Wallet fehlen mir ca. 7,5 BTC! Ich hatte ca. 9 BTC auf meinem Bitcoin Core Wallet und nachddem es einige Probleme mit Überweisungen an Bitcoin.de gab fehlen mit plötzlich ca. 7,5 BTC. Wenn man die Transaktionen durchschaut sieht man, dass der Kontostand ca. 9 BTC betragen müsste. Als Kontostand werden allerdings nur ca. 1,5 BTC angezeigt. Kann mir jemand sagen wie ich die BTC wieder bekomme?
  2. Hallo zusammen, ist es möglich mit der aktuellen Bitcoin Core Wallet 0.15.1 per default P2SH (Segwit) auch für Wechselgeld-Adressen zu verwenden? Ich bekomme das irgendwie nicht hin Wenn es da einen Weg gibt, würde ich mich über eine kurze Anleitung freuen - danke!
  3. Hallo Allerseits! Sorry das ich euch hier höchst warscheinlich wieder damit nerven muss, aber ich brauche unbedingt Hilfe bei einer Sache. Ich habe von Bittrex Bitcoins auf mein Core Wallet gesendet. Auf Bittrex steht die Tansaktion auf Complete und in der Blockchain ist sie einerseits grün angezeigt aber anderer Seits auch unbestätigt, genau so wie im Core Wallet die Transaktion unbestätigt bleibt schon seit über 24 Stunden. An der Transaktions-Gebühr kann es nicht liegen, da die von Bittrex bestimmt wird. Es könnte nur an dem liegen, das ich während der Transaktion mein Core Wallet beendet habe. Liegt hier der Fehler oder ist es was anderes und muss nur Geduld haben. Falls ja, was kann ich tun um diese Transaktion komplett noch bestätigt zu bekommen? Kann Ich selber was tun oder kann ich da einen Support schreiben von dem Core Wallet, oder was kann man tun? Ich freue mich für genaue Instruktionen. LG Flo
  4. Zuerst als newbie ein herzliches Hallo in die Forenrunde. Sorry - Ich bin anscheinend zu beschränkt, um auf die Lösung zu kommen, und auch im Netz und im Forum konnte ich keine (für mich verständliche) Antwort finden. - ich habe den BitCoin Core (12.0) downgeloadet und als .zip Datei vorliegen - parallel habe ich eine zugehörige SHA256SUMS.asc runtergeladen Wie verifiziere ich nun bitte die Integrität des Core-Downloads? Kann mir bitte jemand (in einfachen Schritten) erklären, wie ich vorgehen muß. (Falls das hilfreich sein sollte, ich habe mir die neueste Version von 7-zip geladen, die irgendwas mit "CRC SHA" können soll) Ich würde mich über ein Mini-TUT für Doofies freuen und hoffe auf die Gnade eines Verständigen. Danke und Gruß nemo
  5. Bitcoin Core sagt mir neuerdinggs dass keine Blockquellen verfügbar seien und ich 19 Wochen in Rückstand bin. Was kann ich tun? Hier der neuste Debug Log 2015-09-12 21:04:05 Bitcoin version v0.11.0 (2015-07-10 19:23:55 +0200) 2015-09-12 21:04:05 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2015-09-12 21:04:05 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-09-12 21:04:05 Default data directory C:\Users\DenniSophie\AppData\Roaming\Bitcoin 2015-09-12 21:04:05 Using data directory C:\Users\DenniSophie\AppData\Roaming\Bitcoin 2015-09-12 21:04:05 Using config file C:\Users\DenniSophie\AppData\Roaming\Bitcoin\bitcoin.conf 2015-09-12 21:04:05 Using at most 125 connections (2048 file descriptors available) 2015-09-12 21:04:05 Using 4 threads for script verification 2015-09-12 21:04:05 Using wallet wallet.dat 2015-09-12 21:04:05 scheduler thread start 2015-09-12 21:04:05 init message: Verifiziere Wallet... 2015-09-12 21:04:05 CDBEnv::Open: LogDir=C:\Users\DenniSophie\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\DenniSophie\AppData\Roaming\Bitcoin\db.log 2015-09-12 21:04:05 Bound to [::]:8333 2015-09-12 21:04:05 Bound to 0.0.0.0:8333 2015-09-12 21:04:05 Cache configuration: 2015-09-12 21:04:05 * Using 2.0MiB for block index database 2015-09-12 21:04:05 * Using 132.5MiB for chain state database 2015-09-12 21:04:05 * Using 365.5MiB for in-memory UTXO set 2015-09-12 21:04:05 init message: Lade Blockindex... 2015-09-12 21:04:05 Opening LevelDB in C:\Users\DenniSophie\AppData\Roaming\Bitcoin\blocks\index 2015-09-12 21:04:05 Opened LevelDB successfully 2015-09-12 21:04:05 Opening LevelDB in C:\Users\DenniSophie\AppData\Roaming\Bitcoin\chainstate 2015-09-12 21:04:05 Opened LevelDB successfully 2015-09-12 21:04:08 LoadBlockIndexDB: last block file = 263 2015-09-12 21:04:08 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=114, size=44431890, heights=353686...354624, time=2015-04-25...2015-05-02) 2015-09-12 21:04:08 Checking all blk files are present... 2015-09-12 21:04:08 LoadBlockIndexDB: transaction index disabled 2015-09-12 21:04:08 LoadBlockIndexDB: hashBestChain=000000000000000015f0e04ef4d334744e7d99b3548519fcf878d7dffaba0a08 height=353755 date=2015-04-26 04:47:48 progress=0.817364 2015-09-12 21:04:09 init message: Verifiziere Blöcke... 2015-09-12 21:04:09 Verifying last 288 blocks at level 3 2015-09-12 21:04:28 No coin database inconsistencies in last 98 blocks (61306 transactions) 2015-09-12 21:04:28 block index 22762ms 2015-09-12 21:04:28 init message: Lade Wallet... 2015-09-12 21:04:28 nFileVersion = 110000 2015-09-12 21:04:28 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total 2015-09-12 21:04:28 wallet 33ms 2015-09-12 21:04:28 init message: Aktiviere beste Blockkette... 2015-09-12 21:04:28 mapBlockIndex.size() = 374241 2015-09-12 21:04:28 nBestHeight = 353755 2015-09-12 21:04:28 setKeyPool.size() = 100 2015-09-12 21:04:28 mapWallet.size() = 0 2015-09-12 21:04:28 mapAddressBook.size() = 2 2015-09-12 21:04:28 init message: Lade Adressen... 2015-09-12 21:04:28 Loaded 135 addresses from peers.dat 1ms 2015-09-12 21:04:28 dnsseed thread start 2015-09-12 21:04:28 upnp thread start 2015-09-12 21:04:28 net thread start 2015-09-12 21:04:28 addcon thread start 2015-09-12 21:04:28 opencon thread start 2015-09-12 21:04:28 msghand thread start 2015-09-12 21:04:28 init message: Laden abgeschlossen 2015-09-12 21:04:28 GUI: PaymentServer::LoadRootCAs: Loaded 39 root certificates 2015-09-12 21:04:29 receive version message: /Satoshi:0.10.1/: version 70002, blocks=374239, us=176.199.199.101:52156, peer=1 2015-09-12 21:04:29 Added time data, samples 2, offset -1 (+0 minutes) 2015-09-12 21:04:30 receive version message: /Satoshi:0.11.0/: version 70002, blocks=374239, us=176.199.199.101:52160, peer=3 2015-09-12 21:04:30 Added time data, samples 3, offset +7 (+0 minutes) 2015-09-12 21:04:33 receive version message: /Satoshi:0.10.0/: version 70002, blocks=374239, us=176.199.199.101:52176, peer=7 2015-09-12 21:04:33 Added time data, samples 4, offset -1 (+0 minutes) 2015-09-12 21:04:33 receive version message: /Bitcoin XT:0.11.0/: version 70010, blocks=374235, us=176.199.199.101:52180, peer=8 2015-09-12 21:04:33 Added time data, samples 5, offset +0 (+0 minutes) 2015-09-12 21:04:33 nTimeOffset = +0 (+0 minutes) 2015-09-12 21:04:33 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:34 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:35 No valid UPnP IGDs found 2015-09-12 21:04:35 upnp thread exit 2015-09-12 21:04:36 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:37 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:38 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:39 P2P peers available. Skipped DNS seeding. 2015-09-12 21:04:39 dnsseed thread exit 2015-09-12 21:04:39 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:44 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:48 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:48 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:48 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:48 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:48 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:48 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:49 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:51 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:52 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:52 socket recv error Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (10054) 2015-09-12 21:04:52 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:52 socket recv error Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (10054) 2015-09-12 21:04:53 receive version message: /Satoshi:0.11.99/: version 70002, blocks=374239, us=176.199.199.101:52194, peer=9 2015-09-12 21:04:53 Added time data, samples 6, offset +69 (+1 minutes) 2015-09-12 21:04:53 socket recv error Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (10054) 2015-09-12 21:04:54 receive version message: /Satoshi:0.10.2/: version 70002, blocks=374239, us=176.199.199.101:52199, peer=11 2015-09-12 21:04:54 Added time data, samples 7, offset -1 (+0 minutes) 2015-09-12 21:04:54 nTimeOffset = +0 (+0 minutes) 2015-09-12 21:04:54 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:54 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:54 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:04:55 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:01 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:01 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:01 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:01 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:01 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:02 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:02 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:02 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:02 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:08 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:08 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:12 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:14 socket recv error Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (10054) 2015-09-12 21:05:14 ERROR: AcceptToMemoryPool: non-final 2015-09-12 21:05:15 socket recv error Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (10054)
  6. Bitcoin Core 0.11.0 wurde veröffentlicht und steht zum Download bereit: https://bitcoin.org/bin/bitcoin-core-0.11.0/ Dies ist eine neue Hauptversion, die sowohl neue Funktionen als auch Fehlerbehebungen mit sich bringt. Fehler bitte im Ticketing-System von github melden: https://github.com/bitcoin/bitcoin/issues Aktualisierung Vor einer Aktualisierung sollte man immer ein Backup seines Bitcoin-Datenverzeichnisses zur Hand haben! Wenn eine alte Version von Bitcoin Core läuft muß diese zu erst beendet werden. Läuft die alte Version nicht mehr (was ein paar Minuten dauern kann), dann kann die neue Version einfach darüber installiert werden. Windows: Installer laufen lassen, Mac OS X: /Applications/Bitcoin-Qt durch neue Version ersetzen, Linux: bitcoind/bitcoin-qt durch neue Version ersetzen Wichtige Information Zum Zeitpunkt dieser Meldung wird das P2P-Netzwerk mit Transaktionen mit niedriger Gebühr überflutet. Dies führt zu einem aufblähen der MemPool-Größe. Wenn dieses Wachstum des MemPools auf Ihrem System eine problematische Speichernutzung verursacht, ist es möglich, das einige Konfigurationsoptionen geändert werden um dies zu umgehen. Die Zunahme des MemPools kann mit dem Befehl `RPC getmempoolinfo` überwacht werden. Eine besteht darin, die Mindesttransaktionsgebühr `minrelaytxfee` zu erhöhen, die standardmäßig auf 0,00001 eingestellt ist. Dies wird dazu führen, daß Transaktionen mit weniger BTC / kB Gebühr abgelehnt werden, und damit weniger Transaktionen in den MemPool aufgenommen werden. Die andere ist, die Weitergabe von Transaktionen, mit `Limitfreerelay`zu beschränken. Mit dieser Option wird die Anzahl (kB / Minute) eingestellt, bei der kostenlose Transaktionen (mit genügend Priorität) akzeptiert werden. Der Standardwert ist 15. Die Reduzierung dieser Zahl reduziert die Geschwindigkeit, mit der der MemPool durch kostenlosen Transaktionen wachsen kann. Fügen Sie beispielsweise Folgendes in `bitcoin.conf` ein,: minrelaytxfee = 0,00005 limitfreerelay = 5 Robustere Lösungen werden bei späteren Versionen folgen. Erwähnenswerte Änderungen und Änderungsprotokoll (englisch) Notable changes =============== Block file pruning ---------------------- This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. To recap, there are four types of data related to the blockchain in the bitcoin system: the raw blocks as received over the network (blk???.dat), the undo data (rev???.dat), the block index and the UTXO set (both LevelDB databases). The databases are built from the raw data. Block pruning allows Bitcoin Core to delete the raw block and undo data once it's been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or for rescanning the wallet. The block index continues to hold the metadata about all blocks in the blockchain. The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the block index and UTXO databases. The minimum was chosen so that Bitcoin Core will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 blocks on disk. Block pruning works during initial sync in the same way as during steady state, by deleting block files "as you go" whenever disk space is allocated. Thus, if the user specifies 550MB, once that level is reached the program will begin deleting the oldest block and undo files, while continuing to download the blockchain. For now, block pruning disables block relay. In the future, nodes with block pruning will at a minimum relay "new" blocks, meaning blocks that extend their active chain. Block pruning is currently incompatible with running a wallet due to the fact that block data is used for rescanning the wallet and importing keys or addresses (which require a rescan.) However, running the wallet with block pruning will be supported in the near future, subject to those limitations. Block pruning is also incompatible with -txindex and will automatically disable it. Once you have pruned blocks, going back to unpruned state requires re-downloading the entire blockchain. To do this, re-start the node with -reindex. Note also that any problem that would cause a user to reindex (e.g., disk corruption) will cause a pruned node to redownload the entire blockchain. Finally, note that when a pruned node reindexes, it will delete any blk???.dat and rev???.dat files in the data directory prior to restarting the download. To enable block pruning on the command line: - `-prune=N`: where N is the number of MB to allot for raw block & undo data. Modified RPC calls: - `getblockchaininfo` now includes whether we are in pruned mode or not. - `getblock` will check if the block's data has been pruned and if so, return an error. - `getrawtransaction` will no longer be able to locate a transaction that has a UTXO but where its block file has been pruned. Pruning is disabled by default. Big endian support -------------------- Experimental support for big-endian CPU architectures was added in this release. All little-endian specific code was replaced with endian-neutral constructs. This has been tested on at least MIPS and PPC hosts. The build system will automatically detect the endianness of the target. Memory usage optimization -------------------------- There have been many changes in this release to reduce the default memory usage of a node, among which: - Accurate UTXO cache size accounting (#6102); this makes the option `-dbcache` precise where this grossly underestimated memory usage before - Reduce size of per-peer data structure (#6064 and others); this increases the number of connections that can be supported with the same amount of memory - Reduce the number of threads (#5964, #5679); lowers the amount of (esp. virtual) memory needed Fee estimation changes ---------------------- This release improves the algorithm used for fee estimation. Previously, -1 was returned when there was insufficient data to give an estimate. Now, -1 will also be returned when there is no fee or priority high enough for the desired confirmation target. In those cases, it can help to ask for an estimate for a higher target number of blocks. It is not uncommon for there to be no fee or priority high enough to be reliably (85%) included in the next block and for this reason, the default for `-txconfirmtarget=n` has changed from 1 to 2. Privacy: Disable wallet transaction broadcast ---------------------------------------------- This release adds an option `-walletbroadcast=0` to prevent automatic transaction broadcast and rebroadcast (#5951). This option allows separating transaction submission from the node functionality. Making use of this, third-party scripts can be written to take care of transaction (re)broadcast: - Send the transaction as normal, either through RPC or the GUI - Retrieve the transaction data through RPC using `gettransaction` (NOT `getrawtransaction`). The `hex` field of the result will contain the raw hexadecimal representation of the transaction - The transaction can then be broadcasted through arbitrary mechanisms supported by the script One such application is selective Tor usage, where the node runs on the normal internet but transactions are broadcasted over Tor. For an example script see [bitcoin-submittx](https://github.com/laanwj/bitcoin-submittx). Privacy: Stream isolation for Tor ---------------------------------- This release adds functionality to create a new circuit for every peer connection, when the software is used with Tor. The new option, `-proxyrandomize`, is on by default. When enabled, every outgoing connection will (potentially) go through a different exit node. That significantly reduces the chance to get unlucky and pick a single exit node that is either malicious, or widely banned from the P2P network. This improves connection reliability as well as privacy, especially for the initial connections. **Important note:** If a non-Tor SOCKS5 proxy is configured that supports authentication, but doesn't require it, this change may cause that proxy to reject connections. A user and password is sent where they weren't before. This setup is exceedingly rare, but in this case `-proxyrandomize=0` can be passed to disable the behavior. 0.11.0 Change log ================= Detailed release notes follow. This overview includes changes that affect behavior, not code moves, refactors and string updates. For convenience in locating the code changes and accompanying discussion, both the pull request and git merge commit are mentioned. ### RPC and REST - #5461 `5f7279a` signrawtransaction: validate private key - #5444 `103f66b` Add /rest/headers/<count>/<hash>.<ext> - #4964 `95ecc0a` Add scriptPubKey field to validateaddress RPC call - #5476 `c986972` Add time offset into getpeerinfo output - #5540 `84eba47` Add unconfirmed and immature balances to getwalletinfo - #5599 `40e96a3` Get rid of the internal miner's hashmeter - #5711 `87ecfb0` Push down RPC locks - #5754 `1c4e3f9` fix getblocktemplate lock issue - #5756 `5d901d8` Fix getblocktemplate_proposals test by mining one block - #5548 `d48ce48` Add /rest/chaininfos - #5992 `4c4f1b4` Push down RPC reqWallet flag - #6036 `585b5db` Show zero value txouts in listunspent - #5199 `6364408` Add RPC call `gettxoutproof` to generate and verify merkle blocks - #5418 `16341cc` Report missing inputs in sendrawtransaction - #5937 `40f5e8d` show script verification errors in signrawtransaction result - #5420 `1fd2d39` getutxos REST command (based on Bip64) - #6193 `42746b0` [REST] remove json input for getutxos, limit to query max. 15 outpoints - #6226 `5901596` json: fail read_string if string contains trailing garbage ### Configuration and command-line options - #5636 `a353ad4` Add option `-allowselfsignedrootcertificate` to allow self signed root certs (for testing payment requests) - #5900 `3e8a1f2` Add a consistency check `-checkblockindex` for the block chain data structures - #5951 `7efc9cf` Make it possible to disable wallet transaction broadcast (using `-walletbroadcast=0`) - #5911 `b6ea3bc` privacy: Stream isolation for Tor (on by default, use `-proxyrandomize=0` to disable) - #5863 `c271304` Add autoprune functionality (`-prune=<size>`) - #6153 `0bcf04f` Parameter interaction: disable upnp if -proxy set - #6274 `4d9c7fe` Add option `-alerts` to opt out of alert system ### Block and transaction handling - #5367 `dcc1304` Do all block index writes in a batch - #5253 `203632d` Check against MANDATORY flags prior to accepting to mempool - #5459 `4406c3e` Reject headers that build on an invalid parent - #5481 `055f3ae` Apply AreSane() checks to the fees from the network - #5580 `40d65eb` Preemptively catch a few potential bugs - #5349 `f55c5e9` Implement test for merkle tree malleability in CPartialMerkleTree - #5564 `a89b837` clarify obscure uses of EvalScript() - #5521 `8e4578a` Reject non-final txs even in testnet/regtest - #5707 `6af674e` Change hardcoded character constants to descriptive named constants for db keys - #5286 `fcf646c` Change the default maximum OP_RETURN size to 80 bytes - #5710 `175d86e` Add more information to errors in ReadBlockFromDisk - #5948 `b36f1ce` Use GetAncestor to compute new target - #5959 `a0bfc69` Add additional block index consistency checks - #6058 `7e0e7f8` autoprune minor post-merge improvements - #5159 `2cc1372` New fee estimation code - #6102 `6fb90d8` Implement accurate UTXO cache size accounting - #6129 `2a82298` Bug fix for clearing fCheckForPruning - #5947 `e9af4e6` Alert if it is very likely we are getting a bad chain - #6203 `c00ae64` Remove P2SH coinbase flag, no longer interesting - #5985 `37b4e42` Fix removing of orphan transactions - #6221 `6cb70ca` Prune: Support noncontiguous block files - #6256 `fce474c` Use best header chain timestamps to detect partitioning - #6233 `a587606` Advance pindexLastCommonBlock for blocks in chainActive ### P2P protocol and network code - #5507 `844ace9` Prevent DOS attacks on in-flight data structures - #5770 `32a8b6a` Sanitize command strings before logging them - #5859 `dd4ffce` Add correct bool combiner for net signals - #5876 `8e4fd0c` Add a NODE_GETUTXO service bit and document NODE_NETWORK - #6028 `b9311fb` Move nLastTry from CAddress to CAddrInfo - #5662 `5048465` Change download logic to allow calling getdata on inbound peers - #5971 `18d2832` replace absolute sleep with conditional wait - #5918 `7bf5d5e` Use equivalent PoW for non-main-chain requests - #6059 `f026ab6` chainparams: use SeedSpec6's rather than CAddress's for fixed seeds - #6080 `31c0bf1` Add jonasschnellis dns seeder - #5976 `9f7809f` Reduce download timeouts as blocks arrive - #6172 `b4bbad1` Ignore getheaders requests when not synced - #5875 `304892f` Be stricter in processing unrequested blocks - #6333 `41bbc85` Hardcoded seeds update June 2015 ### Validation - #5143 `48e1765` Implement BIP62 rule 6 - #5713 `41e6e4c` Implement BIP66 ### Build system - #5501 `c76c9d2` Add mips, mipsel and aarch64 to depends platforms - #5334 `cf87536` libbitcoinconsensus: Add pkg-config support - #5514 `ed11d53` Fix 'make distcheck' - #5505 `a99ef7d` Build winshutdownmonitor.cpp on Windows only - #5582 `e8a6639` Osx toolchain update - #5684 `ab64022` osx: bump build sdk to 10.9 - #5695 `23ef5b7` depends: latest config.guess and config.sub - #5509 `31dedb4` Fixes when compiling in c++11 mode - #5819 `f8e68f7` release: use static libstdc++ and disable reduced exports by default - #5510 `7c3fbc3` Big endian support - #5149 `c7abfa5` Add script to verify all merge commits are signed - #6082 `7abbb7e` qt: disable qt tests when one of the checks for the gui fails - #6244 `0401aa2` configure: Detect (and reject) LibreSSL - #6269 `95aca44` gitian: Use the new bitcoin-detached-sigs git repo for OSX signatures - #6285 `ef1d506` Fix scheduler build with some boost versions. - #6280 `25c2216` depends: fix Boost 1.55 build on GCC 5 - #6303 `b711599` gitian: add a gitian-win-signer descriptor - #6246 `8ea6d37` Fix build on FreeBSD - #6282 `daf956b` fix crash on shutdown when e.g. changing -txindex and abort action - #6354 `bdf0d94` Gitian windows signing normalization ### Wallet - #2340 `811c71d` Discourage fee sniping with nLockTime - #5485 `d01bcc4` Enforce minRelayTxFee on wallet created tx and add a maxtxfee option - #5508 `9a5cabf` Add RandAddSeedPerfmon to MakeNewKey - #4805 `8204e19` Do not flush the wallet in AddToWalletIfInvolvingMe(..) - #5319 `93b7544` Clean up wallet encryption code - #5831 `df5c246` Subtract fee from amount - #6076 `6c97fd1` wallet: fix boost::get usage with boost 1.58 - #5511 `23c998d` Sort pending wallet transactions before reaccepting - #6126 `26e08a1` Change default nTxConfirmTarget to 2 - #6183 `75a4d51` Fix off-by-one error w/ nLockTime in the wallet - #6276 `c9fd907` Fix getbalance * 0 ### GUI - #5219 `f3af0c8` New icons - #5228 `bb3c75b` HiDPI (retina) support for splash screen - #5258 `73cbf0a` The RPC Console should be a QWidget to make window more independent - #5488 `851dfc7` Light blue icon color for regtest - #5547 `a39aa74` New icon for the debug window - #5493 `e515309` Adopt style colour for button icons - #5557 `70477a0` On close of splashscreen interrupt verifyDB - #5559 `83be8fd` Make the command-line-args dialog better - #5144 `c5380a9` Elaborate on signverify message dialog warning - #5489 `d1aa3c6` Optimize PNG files - #5649 `e0cd2f5` Use text-color icons for system tray Send/Receive menu entries - #5651 `848f55d` Coin Control: Use U+2248 "ALMOST EQUAL TO" rather than a simple tilde - #5626 `ab0d798` Fix icon sizes and column width - #5683 `c7b22aa` add new osx dmg background picture - #5620 `7823598` Payment request expiration bug fix - #5729 `9c4a5a5` Allow unit changes for read-only BitcoinAmountField - #5753 `0f44672` Add bitcoin logo to about screen - #5629 `a956586` Prevent amount overflow problem with payment requests - #5830 `215475a` Don't save geometry for options and about/help window - #5793 `d26f0b2` Honor current network when creating autostart link - #5847 `f238add` Startup script for centos, with documentation - #5915 `5bd3a92` Fix a static qt5 crash when using certain versions of libxcb - #5898 `bb56781` Fix rpc console font size to flexible metrics - #5467 `bc8535b` Payment request / server work - part 2 - #6161 `180c164` Remove movable option for toolbar - #6160 `0d862c2` Overviewpage: make sure warning icons gets colored ### Tests - #5453 `2f2d337` Add ability to run single test manually to RPC tests - #5421 `886eb57` Test unexecuted OP_CODESEPARATOR - #5530 `565b300` Additional rpc tests - #5611 `37b185c` Fix spurious windows test failures after 012598880c - #5613 `2eda47b` Fix smartfees test for change to relay policy - #5612 `e3f5727` Fix zapwallettxes test - #5642 `30a5b5f` Prepare paymentservertests for new unit tests - #5784 `e3a3cd7` Fix usage of NegateSignatureS in script_tests - #5813 `ee9f2bf` Add unit tests for next difficulty calculations - #5855 `d7989c0` Travis: run unit tests in different orders - #5852 `cdae53e` Reinitialize state in between individual unit tests. - #5883 `164d7b6` tests: add a BasicTestingSetup and apply to all tests - #5940 `446bb70` Regression test for ResendWalletTransactions - #6052 `cf7adad` fix and enable bip32 unit test - #6039 `734f80a` tests: Error when setgenerate is used on regtest - #6074 `948beaf` Correct the PUSHDATA4 minimal encoding test in script_invalid.json - #6032 `e08886d` Stop nodes after RPC tests, even with --nocleanup - #6075 `df1609f` Add additional script edge condition tests - #5981 `da38dc6` Python P2P testing - #5958 `9ef00c3` Add multisig rpc tests - #6112 `fec5c0e` Add more script edge condition tests ### Miscellaneous - #5457, #5506, #5952, #6047 Update libsecp256k1 - #5437 `84857e8` Add missing CAutoFile::IsNull() check in main - #5490 `ec20fd7` Replace uint256/uint160 with opaque blobs where possible - #5654, #5764 Adding jonasschnelli's GPG key - #5477 `5f04d1d` OS X 10.10: LSSharedFileListItemResolve() is deprecated - #5679 `beff11a` Get rid of DetectShutdownThread - #5787 `9bd8c9b` Add fanquake PGP key - #5366 `47a79bb` No longer check osx compatibility in RenameThread - #5689 `07f4386` openssl: abstract out OPENSSL_cleanse - #5708 `8b298ca` Add list of implemented BIPs - #5809 `46bfbe7` Add bitcoin-cli man page - #5839 `86eb461` keys: remove libsecp256k1 verification until it's actually supported - #5749 `d734d87` Help messages correctly formatted (79 chars) - #5884 `7077fe6` BUGFIX: Stack around the variable 'rv' was corrupted - #5849 `41259ca` contrib/init/bitcoind.openrc: Compatibility with previous OpenRC init script variables - #5950 `41113e3` Fix locale fallback and guard tests against invalid locale settings - #5965 `7c6bfb1` Add git-subtree-check.sh script - #6033 `1623f6e` FreeBSD, OpenBSD thread renaming - #6064 `b46e7c2` Several changes to mruset - #6104 `3e2559c` Show an init message while activating best chain - #6125 `351f73e` Clean up parsing of bool command line args - #5964 `b4c219b` Lightweight task scheduler - #6116 `30dc3c1` [OSX] rename Bitcoin-Qt.app to Bitcoin-Core.app - #6168 `b3024f0` contrib/linearize: Support linearization of testnet blocks - #6098 `7708fcd` Update Windows resource files (and add one for bitcoin-tx) - #6159 `e1412d3` Catch errors on datadir lock and pidfile delete - #6186 `182686c` Fix two problems in CSubnet parsing - #6174 `df992b9` doc: add translation strings policy - #6210 `dfdb6dd` build: disable optional use of gmp in internal secp256k1 build - #6264 `94cd705` Remove translation for -help-debug options - #6286 `3902c15` Remove berkeley-db4 workaround in MacOSX build docs - #6319 `3f8fcc9` doc: update mailing list address Credits ======= Thanks to everyone who directly contributed to this release: - 21E14 - Adam Weiss - Alex Morcos - ayeowch - azeteki - Ben Holden-Crowther - bikinibabe - BitcoinPRReadingGroup - Blake Jakopovic - BtcDrak - charlescharles - Chris Arnesen - Ciemon - CohibAA - Corinne Dashjr - Cory Fields - Cozz Lovan - Daira Hopwood - Daniel Kraft - Dave Collins - David A. Harding - dexX7 - Earlz - Eric Lombrozo - Eric R. Schulz - Everett Forth - Flavien Charlon - fsb4000 - Gavin Andresen - Gregory Maxwell - Heath - Ivan Pustogarov - Jacob Welsh - Jameson Lopp - Jason Lewicki - Jeff Garzik - Jonas Schnelli - Jonathan Brown - Jorge Timón - joshr - jtimon - Julian Yap - Luca Venturini - Luke Dashjr - Manuel Araoz - MarcoFalke - Matt Bogosian - Matt Corallo - Micha - Michael Ford - Mike Hearn - mrbandrews - Nicolas Benoit - paveljanik - Pavel Janík - Pavel Vasin - Peter Todd - Philip Kaufmann - Pieter Wuille - pstratem - randy-waterhouse - rion - Rob Van Mieghem - Ross Nicoll - Ruben de Vries - sandakersmann - Shaul Kfir - Shawn Wilkinson - sinetek - Suhas Daftuar - svost - Thomas Zander - Tom Harding - UdjinM6 - Vitalii Demianets - Wladimir J. van der Laan And all those who contributed additional code review and/or security research: - Sergio Demian Lerner As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
  7. Die ausführbaren Dateien für Bitcoin Core Version 0.11.0rc1 sind nun erhältlich: https://bitcoin.org/bin/bitcoin-core-0.11.0/test/ Der Quelltext kann unter der Kennzeichnung (tag) 'v0.11.0rc1' bei github heruntergeladen werden. Die vorläufigen Änderungen finden sich hier: (englisch) https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md
  8. Bitcoin Core 0.10.2 wurde veröffentlicht und steht zum Download bereit: https://bitcoin.org/bin/bitcoin-core-0.10.2/ Dies ist eine neue Unterversion die Fehlerbehebungen und überarbeitete Übersetzungen mit sich bringt. Es wird empfohlen auf diese Version zu aktualisieren. Fehler bitte im Ticketing-System von github melden: https://github.com/bitcoin/bitcoin/issues Erwähnenswerte Änderungen Es wurde ein ernsthaftes Problem unter Windows behoben, betreffend Datenverzeichnissen mit nicht-ASCII-Zeichen im Namen (https://github.com/bitcoin/bitcoin/issues/6078). Für andere Platformen gibt es keine erwähnenswerten Änderungen. Die aufgeführten Änderungen auf Englisch: 0.10.2 Change log Detailed release notes follow. This overview includes changes that affect external behavior, not code moves, refactors or string updates. Wallet: - 824c011 fix boost::get usage with boost 1.58 Miscellaneous: - da65606 Avoid crash on start in TestBlockValidity with gen=1. - 424ae66 don’t imbue boost::filesystem::path with locale “C” on windows (fixes #6078)
  9. Hallo, bin Anfänger in Sachen Bitcoins und habe eine naive Frage bzgl Aufladung Wallet. Habe mir vor einigen Tagen ein Konto auf bitcoin.de zugelegt, und der Kauf von Bitcoins hat auch funktioniert. Jetzt habe ich Bitcoin Core als Wallet runtergeladen. Ich möchte Bitcoins verschicken, bzw was kaufen. Frage: Wie bekomme ich die Bitcoins von meinem Bitcoin.de Konto auf das Wallet? Oder ist bitcoin.de nur ein reiner Handels-Marktplatz? Und wie geht das versenden technisch vom Wallet? (Habe die Frage auch an bitcoin.de gesendet, soweit ohne Antwort) Vielen Dank
×
×
  • Neu erstellen...

Wichtige Information

Wir speichern Cookies auf Ihrem Gerät, um diese Seite besser zu machen. Sie können Ihre Cookie-Einstellungen anpassen, ansonsten gehen wir davon aus, dass Sie damit einverstanden sind. In unseren Datenschutzerklärungen finden sie weitere Informationen.