How do I revoke a transaction.

Wed, 27 Jul 2016 09:46:26 +0000

I understand that blocks in a blockchain if there has been confirmations or if more number of blocks are added after it cannot be modified.
If I am the admin, will I be able to stop the nodes being added temporarily and probably delete an erronoes transaction in a node or maybe isolate the whole block and ask the sender to re-do the transaction?
how do i even modify a newly created block evenif there are no blocks added to it?
who has the control? or is it not controllable by anyone?

Corrupted block database detected.

Tue, 22 Mar 2016 09:20:40 +0000

In the scenario where we have 3 nodes, lets say we made node 1 first then node 2 then 3. Nodes 2 and 3 are replicas of 1. If we insert assets from node 2 into the wallet of node 1 the assets are generated at a
high rate. At one point during "insert from 2 to 1" speed at which assets were being inserted dropped significantly (it seems that node 1 was choking) then node 1 crashed and speed of inserting got back to high.

when i tried to restart node 1 i got an error saying :

: Corrupted block database detected.

Please restart multichaind with reindex=1.

i assume this was probably a hardware glitch or something but i wanted to ask you what can cause this error and also what causes the "choke" that caused node 1 to crash in the first place? Should we add a small sleeep(5s) every 100 sec or so to avoid this or something?

debug log:

2016-03-22 08:55:48 MultiChain version build 1.0 alpha 18 protocol 10005 (2016-03-13 08:58:54 +0200)
2016-03-22 08:55:48 Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
2016-03-22 08:55:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-03-22 08:55:48 Default data directory /home/sloba/.multichain/theone
2016-03-22 08:55:48 Using data directory /home/sloba/.multichain/theone
2016-03-22 08:55:48 Using config file /home/sloba/.multichain/theone/theone.conf
2016-03-22 08:55:48 Using at most 125 connections (1024 file descriptors available)
2016-03-22 08:55:48 Using 4 threads for script verification
2016-03-22 08:55:48 Using wallet wallet.dat
2016-03-22 08:55:48 init message: Verifying wallet...
2016-03-22 08:55:48 CDBEnv::Open : LogDir=/home/sloba/.multichain/theone/database ErrorFile=/home/sloba/.multichain/theone/db.log
2016-03-22 08:55:49 init message: Initializing multichain...
2016-03-22 08:55:50 nFileVersion = 100000
2016-03-22 08:55:50 Keys: 3 plaintext, 0 encrypted, 3 w/ metadata, 3 total
2016-03-22 08:55:50 mchn: Parameter set is valid - initializing blockchain parameters...
2016-03-22 08:55:50 Binding RPC on address ::1 port 7724 (IPv4+IPv6 bind any: 0)
2016-03-22 08:55:50 Binding RPC on address 127.0.0.1 port 7724 (IPv4+IPv6 bind any: 0)
2016-03-22 08:55:50 Bound to [::]:7725
2016-03-22 08:55:50 Bound to 0.0.0.0:7725
2016-03-22 08:55:50 init message: Loading block index...
2016-03-22 08:55:50 Opening LevelDB in /home/sloba/.multichain/theone/blocks/index
2016-03-22 08:55:50 Opened LevelDB successfully
2016-03-22 08:55:50 Opening LevelDB in /home/sloba/.multichain/theone/chainstate
2016-03-22 08:55:50 Opened LevelDB successfully
2016-03-22 08:55:50 LoadBlockIndexDB: last block file = 0
2016-03-22 08:55:50 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1404, size=16787062, heights=0...1396, time=2016-03-21...2016-03-22)
2016-03-22 08:55:50 Checking all blk files are present...
2016-03-22 08:55:50 LoadBlockIndexDB(): transaction index enabled
2016-03-22 08:55:51 LoadBlockIndexDB(): hashBestChain=00004bfc0db5821879c2b167ba2c6cefe8c18320b5eabb9043d2032dcf178dcb height=1396 date=2016-03-22 08:20:46 progress=1.000000
2016-03-22 08:55:51 init message: Verifying blocks...
2016-03-22 08:55:51 Verifying last 288 blocks at level 3
2016-03-22 08:55:51 ERROR: VerifyDB() : *** found bad permission data at 1396, hash=00004bfc0db5821879c2b167ba2c6cefe8c18320b5eabb9043d2032dcf178dcb

2016-03-22 08:55:51 : Corrupted block database detected.

Please restart multichaind with reindex=1.
2016-03-22 08:55:51 Aborted block database rebuild. Exiting.
2016-03-22 08:55:51 Shutdown: In progress...
2016-03-22 08:55:51 StopNode()
2016-03-22 08:55:51 Node stopped
2016-03-22 08:55:51 Shutdown: done
2016-03-22 08:55:51 CDBEnv::EnvShutdown : Error 22 shutting down database environment: Invalid argument

No new blocks, broken wallet

Mon, 21 Mar 2016 19:08:53 +0000

We have a "single node" Multichain running, but after a reboot we had to run the daemon with "-salvagewallet" because it say it has a broken wallet.

The main issue right now it that the networks is not creating new blocks, so new transactions get stuck on mempool

debug.log says something about mining, but we dont have mining at all, all the funds where send to an address on first block

2016-03-21 15:59:54 mapAddressBook.size() = 1
2016-03-21 15:59:54 init message: Loading addresses...
2016-03-21 15:59:54 Loaded 0 addresses from peers.dat 0ms
2016-03-21 15:59:54 init message: Done loading
2016-03-21 15:59:54 Node started
2016-03-21 15:59:54 dumpaddr thread start
2016-03-21 15:59:54 BitcoinMiner started
2016-03-21 15:59:54 mchn: Cannot find address having mining permission
2016-03-21 15:59:54 msghand thread start

How can we fix this?

Thanks

Which impact creating block mid-insert has on insertion?

Thu, 10 Mar 2016 14:19:40 +0000

MultiChain Developer Q&A - Recent questions tagged creating-blocks

How do I revoke a transaction.

Corrupted block database detected.

No new blocks, broken wallet

Which impact creating block mid-insert has on insertion?