Skip to content
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

Unexpected deposit event duplicates after privatenet node 0.9.12 update. #4095

Closed
bors2908 opened this issue Oct 22, 2021 · 3 comments
Closed

Comments

@bors2908
Copy link

Hi!

Recently I've been testing an 0.9.12 node update and found a strange issue with api.query.system.events.at()

If I am sending a multisig transaction and trying to monitor respective events, API returns new unexpected ones:
duplicates

  • second Deposit balances event with the same content
  • new Deposit balances event which has the same amount as the Deposit treasury event

and unknown events

  • new Deposit balances event with unknown amount (does not include as a fee) and main cosigner address in it.

which were not the case with 0.9.11 node. Issue was confirmed on 6.4.1 and 6.4.2 API versions. Events examples below.

Thank you!

Example events list in 0.9.11:

After 1st multisig tx

{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'treasury',
index: '0x1306',
data: [ '192,779,719' ]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0504',
data: [
'15Jbynf3EcRqdHV1K14LXYh7PQFTbp5wiXfrc4kbMReR9KxA',
'48,194,930'
]
},
topics: []
}

After 2nd multisig tx

{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'treasury',
index: '0x1306',
data: [ '264,353,161' ]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0504',
data: [
'15Jbynf3EcRqdHV1K14LXYh7PQFTbp5wiXfrc4kbMReR9KxA',
'66,088,291'
]
},
topics: []
}

0.9.12

After 1st multisig tx

{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'14in5CMUV7RnkDUQzPtPSJEqpo3xQ2aQe8u4GFcfzBCforJ3',
'76,166,438'
]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB',
'192,377,849'
]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'treasury',
index: '0x1306',
data: [ '192,377,849' ]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'15Jbynf3EcRqdHV1K14LXYh7PQFTbp5wiXfrc4kbMReR9KxA',
'48,094,463'
]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'15Jbynf3EcRqdHV1K14LXYh7PQFTbp5wiXfrc4kbMReR9KxA',
'48,094,463'
]
},
topics: []
}

After 2nd multisig tx

{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB',
'263,868,060'
]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'treasury',
index: '0x1306',
data: [ '263,868,060' ]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'15Jbynf3EcRqdHV1K14LXYh7PQFTbp5wiXfrc4kbMReR9KxA',
'65,967,016'
]
},
topics: []
}
{
phase: { ApplyExtrinsic: '2' },
event: {
method: 'Deposit',
section: 'balances',
index: '0x0507',
data: [
'15Jbynf3EcRqdHV1K14LXYh7PQFTbp5wiXfrc4kbMReR9KxA',
'65,967,016'
]
},
topics: []
}

@jacogr
Copy link
Member

jacogr commented Oct 22, 2021

The API simply decodes what the Node supplies, nothing more.

@jacogr
Copy link
Member

jacogr commented Oct 25, 2021

Substrate tracking paritytech/polkadot#4133

@jacogr jacogr closed this as completed Oct 25, 2021
@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Nov 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants