-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with a new coin - Cannot read property 'scriptPubKey' of undefined #461
Comments
Are you able to post a link to the coin wallet so I can test this myself? Or can you post the raw transaction data for the tx that is causing this problem? It will help a lot to determine WHY this is failing. What I do see based on the error msg is that the problem transaction is dying on If you're desperate to get past the error, a hacky fix might be to simply check if any vouts exist first before continuing to check the vout data. I do not recommend this "fix" because it would be better to diagnose WHY your transaction has no recipients and correct that problem, but you could try changing
to:
If you do try this "fix", please keep in mind that this will likely skew your totals since it's not able to properly read the data and is effectively just skipping the transaction. |
Do you need this? getblock acec023e999d562adf7b51fcac047d94fa8f08da8f833ea62f1466b841ea4236
|
Almost, but I don't need the block data, I need the transaction data. Based on what you have shared so far, it looks like block 10285 has three transactions and only two of them synced properly before dying on the 3rd. I think this will reveal the correct data:
|
Here it is !
|
Thanks for posting the transaction data, the problem is very clear now. Transaction Unfortunately, this explorer only supports standard blockchain data which means you will most likely need to add your own implementation of the privacy features. I'm curious, which coin is this cloned from or what privacy technology is it using? Perhaps you can get lucky and find another explorer that already added support for such privacy tech if you search for it. |
New coin is based on PIVX 5.1, latest version |
I've never tried this myself but this might be the best explorer to use for your coin until someone adds pivx support to iquidus or another explorer: https://github.com/random-zebra/PIVX-BlockExplorer |
I know that but it requires more powerful server than Iquidus |
Unfortunately I doubt there may be much we can do. This would require quite a number of rewrites to block parsing to throw catches in there for this type of usecase (same with other privacy coins like XMR for instance). While I would love to say that we'd just need to edit the same function that's handling #56, I doubt it'd be enough. I'm going to close this for now, but it's definitely a thing that may need to be revisited if someone else can come up with an implementation idea. |
Hi, we are developing a new coin and we get a problem with Explorer
10283: 36b8f4e6ba98cb5bbcbf89ff512c57ae8b3218ade1d2f0f49930771674a21886
10284: 760c124c751749f89828f41095515cdbe21097bf2706054394d3d7204216d29b
10284: 98f4bfee66a547cfcc7020e8755175dbc1d8fe3fe46316030889ca2e877b99a2
10285: b906dd8632f668b1e006812806a2be2985e66f8fde60ecc285ac571d37952671
10285: 5fb10f60dc5e0c22f2170c52271f5d7845f914cf78d040e9839e6c22da454e6a
/root/explorer/node_modules/bluebird/js/release/async.js:49
fn = function () { throw arg; };
^
TypeError: Cannot read property 'scriptPubKey' of undefined
at /root/explorer/lib/explorer.js:523:19
at Object.next (/root/explorer/lib/explorer.js:365:24)
at Object.syncLoop (/root/explorer/lib/explorer.js:376:10)
at Object.prepare_vout (/root/explorer/lib/explorer.js:497:20)
at /root/explorer/lib/database.js:117:13
at /root/explorer/lib/explorer.js:605:14
at Object.next (/root/explorer/lib/explorer.js:365:24)
at Object.syncLoop (/root/explorer/lib/explorer.js:376:10)
at Object.prepare_vin (/root/explorer/lib/explorer.js:582:20)
at /root/explorer/lib/database.js:116:11
at /root/explorer/lib/explorer.js:207:16
at Client. (/root/explorer/lib/explorer.js:29:14)
at Client.tryCatcher (/root/explorer/node_modules/bluebird/js/release/util.js:16:23)
at Promise.successAdapter (/root/explorer/node_modules/bluebird/js/release/nodeify.js:23:30)
at Promise._settlePromise (/root/explorer/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/root/explorer/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/root/explorer/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/root/explorer/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/root/explorer/node_modules/bluebird/js/release/promise.js:466:57)
at Promise._settlePromiseFromHandler (/root/explorer/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/root/explorer/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/root/explorer/node_modules/bluebird/js/release/promise.js:649:10)
I have already used tip from issue #56
Any help is appreciated!
The text was updated successfully, but these errors were encountered: