#Failed to sign boxes due to assertion failed Tree root should be real but was UnprovenSchnorr
1 messages · Page 1 of 1 (latest)
it usually means that you trying to sign a box that you don't own
Seems to be the same problem as #1017306523778678804
Looks like it's unlocked - is the node at the correct height? What does /info say ?
mna
{
"currentTime": 1666741662266,
"network": "mainnet",
"name": "ergo-mainnet-4.0.105",
"stateType": "utxo",
"difficulty": 6382561920024576,
"bestFullHeaderId": "7c456bfe5236a3e867ec08bb32e99dc637e9833e24082ecbdda0957ab182575d",
"bestHeaderId": "7c456bfe5236a3e867ec08bb32e99dc637e9833e24082ecbdda0957ab182575d",
"peersCount": 30,
"unconfirmedCount": 13,
"appVersion": "4.0.105",
"eip37Supported": true,
"stateRoot": "5f80383d41942aafe3adc3a6165fe19ffc285bbdf00958aea51972f316e3b11519",
"genesisBlockId": "b0244dfc267baca974a4caee06120321562784303a8a688976ae56170e4d175b",
"previousFullHeaderId": "c6188f5bb91fb31cc00b571668ba95c38473714049aeccf75ba8f294d2106d98",
"fullHeight": 860711,
"headersHeight": 860711,
"stateVersion": "7c456bfe5236a3e867ec08bb32e99dc637e9833e24082ecbdda0957ab182575d",
"fullBlocksScore": 1.240663566636286e+21,
"maxPeerHeight": 860711,
"launchTime": 1666729672867,
"lastSeenMessageTime": 1666741646985,
"eip27Supported": true,
"headersScore": 1.240663566636286e+21,
"parameters": {
"outputCost": 184,
"tokenAccessCost": 100,
"maxBlockCost": 8001091,
"height": 860160,
"maxBlockSize": 1271009,
"dataInputCost": 100,
"blockVersion": 2,
"inputCost": 2271,
"storageFeeFactor": 1250000,
"minValuePerByte": 360
},
"isMining": true
}
Wallet Status
"isInitialized": true,
"isUnlocked": true,
"changeAddress": "9h9jaKchSSQDNpMTtevaGbqY1K9fpMD8FMb7GzjGcMMxFdLbK2C",
"walletHeight": 860734,
"error": ""
}```
is this a lost cause?
Not sure whats up, can you post logs as a git issue onto the node repo?
I am not proficient with github
can you send logs here? And then delete the .ergo/state and .ergo/history and resync
which logs you want? all? or is there a specific
I also did delete /state and /history and it is resyncing including headers
tail -Fn+0 ergo.log | grep 'ERROR\|WARN' > output.log
I am going to put them up on github the repo is private so I need your username
23:47:22.464 ERROR [ef-critical-dispatcher-33] o.e.m.CandidateGenerator$ - Failed to produce proofs for transactions, but emission box is found:
java.lang.Exception: Key XXXXXXXXXX does not exist
UTXO. f2b265764c3ffb56a74d67f266537ad08dfe49b1fd1751f3f4ebc3239224b224: 0 == 1:
scorex.core.validation.MalformedModifierError: Every input of the transaction should be in UTXO.
23:47:22.597 ERROR [ef-critical-dispatcher-33] o.e.m.CandidateGenerator - Candidate generation failed
java.lang.IllegalArgumentException: Proofs for 0 txs cannot be generated : emissionTxs: 1, priorityTxs: 0, poolTxs: 0
that seems to be the repeating error list
I can create more address's but not send.
they are unspent boxes if that means anything
glasgowm148
Is this erg you solo mined by chance?
yea
Do you have
ergo {
wallet {
checkEIP27 = true
}
}
In your ergo.conf ?
EIP-27 got successfully activated @ block # 777,217 . Now the biggest question for pools and miners is how to handle rewards and payments. In the first place, note that emission in Ergo is done via a contract (releasing ERGs each block according to a schedule set in the contract). After EIP-27 soft-fork, re-emission tokens are attached to mini...
no I do not
I added that and now I will restart the node
12:15:43.922 INFO [main] org.ergoplatform.ErgoApp - EIP27 activation height: 777217
now the ergo balance has changed
I still get the same error when sending ergo.
This on a fresh sync? Did you invite me to your log repo?
You can also always restore on a normal wallet and retrieve your funds that way btw
I added you my log files are well over 25mb limit of github so I uploaded the first part of the log after the sync
should I start a new sync after writing that into the config file? I know I can restore but I did that one thing no one is suppose to do even though I know I copied it. I always copy those mnemonic's even if they are not important.
If it comes down to creating a new wallet I would rather burn whats left in that wallet before I loose it all lol
wdym? You can just restore with your seed on another wallet. And also erg can't be burnt 🙂
config change shouldn't need a fresh sync; meant since the original error