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

How do 'Sphinx' invoice-less payments on the Lightning Network work?

How do 'Sphinx' invoice-less payments on the Lightning Network work? There was recently a WIP draft published to the lnd Github, for a 'Sphinx payment mode' for Lightning Network nodes. To quote Roasbeef from the Github PR : [this allows] the ability to send a payment to a destination without first needing to have an invoice Though this is a WIP, it can apparently be used on mainnet already, as long as all nodes involved are upgraded to include the new code. So how does this work? At a high level, what does the UX look like? At a low level, what differences are there in terms of completing the payment (passing HTLCs around), compared to a standard LN transaction? Whats going on under the hood? http://bit.ly/2FoFIgP
Read more

How public key is calculated from a base58 encoded private key?

How public key is calculated from a base58 encoded private key? I followed this post and created a private key for bitcoin wallet. The post says after finding the random 256 bit(32 bytes) integer the version number should be prepended and the checksum should be appended to it. This produces a 37 bytes hex. Now I am trying to find the public key associated with this private key.I learnt that the PUBLIC key is calculated by applying ECDSA secp256k1 curve on the private key. But only 32 bytes is accepted as input by the ECDSA algorithm. So what am I doing wrong? Thanks in advance. http://bit.ly/2AvHLvg
Read more

QUESTION ABOUT SLOW API

QUESTION ABOUT SLOW API do you know about api requests cryptocurrency exchanges? Simple ticker request may be viewed like this: https://api.kucoin.com/v1/open/tick or like this: https://www.okex.com/api/v1/ticker.do?symbol=ltc_btc Different: in first case we get info about all currencies in one request and then pick up certain symbols and parameters, we need. Symbols are the keys of dictionaries or lists and other params are their values. In second case I should create new request for each currencies I considering. Is it neccesary? If I consider, for instance 60 symbols, and do operations with them in Python - programm bot become slow enough. One-two ticker requests are long about 30 sec - for compare, in first case - 5 sec. How can I solve this problem? Thanks. http://ift.tt/2HpiAM0
Read more