search

failure

Hi guys any idea the meaning of this error "FAILURE_PAST_DEADLINE" ??

I just put this in as a bounty because I have asked everyone I can think of to address this for months. I believe this should not be a project for each of us to solve but it should be built into the NIS. If you believe so let's be vocal and put it to an importance vote. NIS changes fees by hard forks which always subjects a network to failure. But the Business side of the bug is serious for projects and financial applications that are fee intensive because costs cannot be projected. In other words, if a client is expected to do 25 transactions an hour I can estimate the current price of $0.01 per transaction or $0.25 an hour overhead. I now know I can charge $1 an hour and have $0.25 built in overhead. But if XEM goes up where fees are $0.05 without a fork, my built in overhead just went to $1.25 and hour and I go broke. Solution: Fix NEM fees in NIS to fiat like $0.01 per transaction and read the current price of XEM and adjust the fee in XEM to ($0.01 / XEM price). At $0.20 XEM that would be 0.05 XEM. Now if the price of XEM doubles the fee would be ($0.01 / $0.40) = 0.025 XEM. This once again would still be a fee of $0.01 a transaction even at double the price of XEM. As a game designer, I can feel safe developing knowing 25 transactions in an hour will still have an overhead in my game of $0.25. All fees would be adjusted in NIS to the formula instead of hard coding. Now if you find that transactions at $0.01 is not working for NEM either higher or lower, you do a once in awhile hard fork to change the formula. Say you decide transactions need to be $0.02 each. You make transaction fees ($0.02 / XEM Price) which would be currently $0.02 / $0.20 = 0.1 NEM. I might not be happy, if I built my game at $0.01 fees and it doubled, but I am happier at a cost of $0.50 overhead instead of $1.25 which surely breaks the long term projections. This is a SERIOUS business logic bug, not a programming bug. I have dealt with this problem for years in bitcoin and there is no need to have it in NEM when it is easily fixed. Do not say I can use the private chain, that would cut out most of the small developers you need for adoption on the public chain. This is critical enough it should be build into Catapult from the start. I am sure you have variables for fees at the top of some file. Just make them equations in real time instead of hard-coded. You already track the price of XEM in the NIS.

What is a build tool?

FAILURE: Build failed with an exception.

* Where:
Script '/Users/mizunashi/git/NEMPay/platforms/android/CordovaLib/cordova.gradle' line: 64

* What went wrong:
A problem occurred evaluating root project 'android'.

> No installed build tools found. Install the Android build tools version 19.1.0 or higher.

to prepare a tx using /transaction/prapare-announce, how to set timestamp, I always got the error of 'timestamp_failure_ too_far_in_future'

King Cole
The discussion started with Chronobank stating the Parity wallet bug did not impact Chronobank because they had cocded their own implementation of multi-sig. I posted that they could have just used NEM and used the on-chain solution

I would posit it this way. If they want to run their program on chain it is ok. But if they is a fissure in the system that will be the end of their business. Will they be able to sleep well? I wouldn't be able to sleep at all wondering what's gonna happen if there is a failure or a fork. Not unless I want it to fail and then I can runaway happy making all the money I raised and blame it on the chain. There i s no reason for any business to run a program on chain. It is suicidal. Nevermind how great it is going to be.

just got a message: 'FAILURE_MULTISIG_NOT_A_COSIGNER',

Yep it was a transaction from Cryptopia to Nano. In theory when Cryptopia tried to honour it against a NIS node it should have failed as an invalid address but then it is down to the Cryptopia code as to how they handled the failure

hey guys anybody ever had this error with nem library when transfering mosaics? Error: FAILURE_INSUFFICIENT_FEE

Greetings I am trying to make a transaction on my NEM wallet in the mainet and I get this error: FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE Does anyone know why? How can I solve that?

Hey guys I’m using the NEM node SDK and I keep getting a Failure transaction cache too full and I looked it up in docs and it says that it’s because I am creating too many transactions. Does the server eventually process these transactions? Does it still process the fee for these requests?

I see error FAILURE_INSUFFICIENT_FEE when sending mosaic, is this something new? I did not change the app.

"FAILURE_MOSAIC_DIVISIBILITY_VIOLATED",

hello, does someone know why this error is? I am trying to connect api node with peer node. 2018-07-31 12:00:44.726691 0x00007f9badf13700: (chain::[email protected]) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure 2018-07-31 12:00:47.771232 0x00007f9badf13700: (chain::[email protected]) node interaction failed: Remote_Is_Forked 2018-07-31 12:00:47.771332 0x00007f9badf13700: (chain::[email protected]) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure 2018-07-31 12:00:50.823181 0x00007f9badf13700: (chain::[email protected]) node interaction failed: Remote_Is_Forked 2018-07-31 12:00:50.823296 0x00007f9badf13700: (chain::[email protected]) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure

i am trying to do that i am facing error like message: 'FAILURE_TRANSACTION_NOT_ALLOWED_FOR_MULTISIG',

version: -1744830462, signer: 'ad08666d7ecb4fc65d2f1469794530e75531b55ec13bdcaaaf4103517e2d814e', timeStamp: 108131142, deadline: 108134742, fee: 500000, modifications: [ { modificationType: 1, cosignatoryAccount: '1b72f63f967aa1b160aada9fb3df5fb30bb5ffb6d8b492e38d7c067657035e07' } ], minCosignatories: { relativeChange: 1 } } { host: 'http://23.228.67.85', port: 7890 } ................. { innerTransactionHash: {}, code: 74, type: 1, message: 'FAILURE_TRANSACTION_NOT_ALLOWED_FOR_MULTISIG', transactionHash: { data: '0ddb821ceee53c067e6002baf04e99b5d3cbbbb5adc0e240bc82122bdaa1fef4' } }

version: -1744830462, signer: 'ad08666d7ecb4fc65d2f1469794530e75531b55ec13bdcaaaf4103517e2d814e', timeStamp: 108131142, deadline: 108134742, fee: 500000, modifications: [ { modificationType: 1, cosignatoryAccount: '1b72f63f967aa1b160aada9fb3df5fb30bb5ffb6d8b492e38d7c067657035e07' } ], minCosignatories: { relativeChange: 1 } } { host: 'http://23.228.67.85', port: 7890 } ................. { innerTransactionHash: {}, code: 74, type: 1, message: 'FAILURE_TRANSACTION_NOT_ALLOWED_FOR_MULTISIG', transactionHash: { data: '0ddb821ceee53c067e6002baf04e99b5d3cbbbb5adc0e240bc82122bdaa1fef4' } }

Hash: BD6EF9BC471588E9A234694D6488A3DF3F8E5764F61F8A6604EB17A937D46777 Error code: Failure_Multisig_Operation_Not_Permitted_By_Account Deadline: 2018-11-01 17:53:52.210

Has been any changes to nem-sdk or default nodes? Now all transactions are getting FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE

"message": "FAILURE_WRONG_NETWORK" nem api work??

What time should I use to solve the problem of FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE NisNodeInfo{ node:Node { metaData:NodeMetaData { features:3, network:-104, application:null, version:'0.6.95-BETA', platform:'Oracle Corporation (1.8.0_40) on Linux' }, endpoint:NodeEndpoint { protocol:'http', port:7890, host:'104.128.226.60' }, identity:NodeIdentity { name:'Hi, I am BigAlice2', publicAccount:undefined } }, nisInfo:ApplicationMetaData { currentTime:114793717, application:'NEM Deploy', startTime:114429223, version:'0.6.95-BETA', signer:null } }

What time should I use to solve the problem of FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE NisNodeInfo{ node:Node { metaData:NodeMetaData { features:3, network:-104, application:null, version:'0.6.95-BETA', platform:'Oracle Corporation (1.8.0_40) on Linux' }, endpoint:NodeEndpoint { protocol:'http', port:7890, host:'104.128.226.60' }, identity:NodeIdentity { name:'Hi, I am BigAlice2', publicAccount:undefined } }, nisInfo:ApplicationMetaData { currentTime:114793717, application:'NEM Deploy', startTime:114429223, version:'0.6.95-BETA', signer:null } }

FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE There was no such problem last week. but today, it always appears when I transfer on testnet, What happened?

FAILURE_WRONG_NETWORK

FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE

FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE can someone help me fix this pls ?

https://forum.nem.io/t/failure-timestamp-too-far-in-future-nem-sdk/16512/4

I have the same error 'FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE', I found solution this link https://forum.nem.io/t/failure-timestamp-too-far-in-future-nem-sdk/16512/3. But Where receiveTimeStamp can put ? This is my code

hey guys✌️ i wanna transfer some mosaics, and inget the message : failure_timestamp_too_far_in-future whats wrong how can i solve thiss issue?

do we need to manually calculator transaction_fee for sending mosaic transactions? We are following this example from nem-sdk github [https://github.com/QuantumMechanics/NEM-sdk/blob/master/examples/nodejs/mosaicTransfer.js]. But we are still encountering FAILURE_INSUFFICIENT_FEE error

FAILURE_MOSAIC_DIVISIBILITY_VIOLATED

I'm using https://nemproject.github.io/nem-library-docs/ and recently day, I got issue with FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE when announceTransaction. Images below.
cryptoBeliever
Because nem-library is using local time and your time is not ahead of NIS time anymore ;)

anyway I think that's a way to fix FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE, you can just check your minute and dont have to care about the hou

anyone who I can discuss multisig transaction timestams with? :) I was looking into why I kept getting nanowallet failures to submit multisig transactions on a testnet

Hello! I'm following this example (https://github.com/QuantumMechanics/NEM-sdk/blob/master/examples/nodejs/mosaicTransfer.js), put my private key and the Mosaic I want to send, but I get this error FAILURE_INSUFFICIENT_FEE. Will someone know how to solve the problem?

Hi guys, I have posted a workaround for the Timestamp failure in the Forum for nemsdk users

Im trying to send Dim-Zar or any XEm mosaics its results me in error called ' failure_timestamp_too_far_in_future'. And I have dim coins when I open and see in nanowallet app in desktop. I backed same wallet and imported in mobile app 'dimpay' its not showing mosaics . what is the issue ? can anyone assist me

@evias I have tried with broadcast example . I am getting failure wrong network error

greg evias
the private key used by nem wallet, then that private key you can also use with nem-php

I gave private key in constructor also . on broadcast im getting some result and also tried in postman too. still its throwing error like FAILURE_NETWORK

cryptoBeliever
https://github.com/evias/nem-php 🙂 can be installed with composer, its better for laravel but can be used without

I have checked this. there is no transaction code from someother way I tried that also throwing Network_failure error

https://forum.nem.io/t/initiating-transactions-returns-failure-wrong-network/1855/11
cryptoBeliever
Yes.

Okie now its thrwing this error FAILURE_SIGNATURE_NOT_VERIFIABLE

FAILURE_SIGNATURE_NOT_VERIFIABLE

What to do if im getting error FAILURE_SIGNATURE_NOT_VERIFIABLE

https://github.com/NemProject/nem-library-ts/pull/4fixed FAILURE_TIMESTAMP_TOO_FAR_IN_FUTURE feel free review and feeback 🙂

Anyone here who fixed this error FAILURE_INSUFFICIENT_FEE using browser and nem-sdk ?

Hi, so I decided to go with Nodejs SDK. Its working but I have an error. I created an mosaic with no fee, but I get the following erro when sending{ innerTransactionHash: {}, code: 17, type: 1, message: 'FAILURE_INSUFFICIENT_FEE', transactionHash: { data: '54e2968b58c44c12f358042b8e736edb5dda0a177d53124670e9da4ce989be06' } }even if I putpreparedTransaction.fee = null;stil doesnt work, It only works if I put a fee and its in xem. So what can I do to send my coin without any fees, even without nem fee.

Alguien sabe xq me da el error failure lock invalid mosaic id al hacer una transacción con lock funds? Uso XEM.createRelative(10)