Ignis transaction not included in the blockchain

Ignis transaction not included in the blockchain

The following transaction submitted to the Ardor blockchain remained unconfirmed and eventually expired, what is the the reason for this?

{
  "senderPublicKey": "...",
  "isBundled": false,
  "chain": 2,
  "signature": "3a49a35627b4ce8a5ac2822b35818f907aec4fd53e79fb02d900d88c0f991c0d71973c434ccaad318a1288a1fb64e53d20dc30de74beb18520c5f4bce06372d4",
  "feeNQT": "100000000",
  "requestProcessingTime": 0,
  "type": 0,
  "fullHash": "552ec333deb265d60ccfa4225123106ce4fc8f9a751185c561083b4cd9b14ed3",
  "version": 1,
  "fxtTransaction": "0",
  "phased": false,
  "ecBlockId": "18397966223991632613",
  "signatureHash": "72caad33596e08e67fe43f42033c0223f9abec9b440b10c07cfd186a037eb972",
  "attachment": {
    "version.OrdinaryPayment": 0
  },
  "senderRS": "...",
  "subtype": 0,
  "amountNQT": "77470950921",
  "sender": "12661870821659068934",
  "recipientRS": "ARDOR-LHJR-WZVF-VKTX-3PVAA",
  "recipient": "1451133144082759191",
  "ecBlockHeight": 384416,
  "deadline": 60,
  "timestamp": 22957813,
  "height": 2147483647
}
https://ift.tt/2Q1gw0X

Comments

Post a Comment

Popular posts from this blog

Do extra hop channels in a BOLT#11 invoice need to exist on chain?

Do extra hop channels in a BOLT#11 invoice need to exist on chain? According to the BOLT#11 specification, a node may add extra routing information for private channels to an invoice, where they specify the public key of the penultimate hop, along with the short_channel_id. r (3): data_length variable. One or more entries containing extra routing information for a private route; there may be more than one r field pubkey (264 bits) short_channel_id (64 bits) ... However, unlike channels announced through a channel_announcement message, there are no signatures to prove that the invoice payee actually owns that channel, or even that it really exists. Technically, it appears that the invoice creator could point to any valid 2-of-2 UTXO on the chain and claim it to be their private channel. Do existing implementations check whether the transaction referred to by the r field's short_channel_id actually exists on the blockchain and that they are valid 2-of-2 multisig transaction...
Read more

What exactly is a block?

What exactly is a block? I am trying to understand the Blockchain algorithm used in Bitcoin. I do not get the part how blocks are created. Let’s say transactions occur at some time. Then, if some nodes get these transactions, these verify the transactions are valid and then send it to other nodes. With this verify-send algorithm, almost every node verifies these newly occurred transactions in few seconds. Now, it is a time for a miner to do his job, which I do not understand. He needs to find a nonce which makes a lower value than hash values given in transactions. Question 1 How many transactions should a miner should verify in a single block? For example, if a miner A finds a nonce which gives a lower value than hash values given in 50 transactions, and if a miner B finds a nonce which gives a lower value than hash values given in 70 transacations, would a reward be given only to the miner B? So should a miner appropriately choose how many transacations he will work for? Ques...
Read more

New 22 THS Bitcoin ASIC Miner, the Holic H22

Image
New 22 THS Bitcoin ASIC Miner, the Holic H22 It seems that there is more competition coming up on the Bitcoin ASIC market with the announcement of the Holic H22 Bitcoin ASIc miner that is supposed to deliver 22 THS of hash power at 1600 Watts of power usage. The ASIC chips inside the device are based on 10nm technology from Samsung. These new ASIC miners are being developed by a Greek company for their own mining farms (capacity 15 MW in locations), but they also put them up for pre-order for other customers that might be interested. The only drawback is that delivery of the Holic Tec H22 ASIC miners is set for mid to late December and by that time the competition will have similar products on the market already. Holic H22 ASIC Specifications: – Hash rate: 22 THS (tolerance ± 5%) – Number of chips: 161 – Power consumption: 1600W – Operating voltage: 11.6 ~ 13V – Cooling: 2x 190 CFM Fans – Operating temperature: 0–45 °C – Dimensions: 175mm x 189mm x 420mm – Network connection...
Read more