TPID was not processed when provided in addaddress about fio

[aaroncox]

Edit: Disregard, this is incorrect (see below)

Seeing the same thing using our internal tooling.

I submitted a transaction for regaddress which included a tpid on mainnet, and the table within fio.tpid remained empty.

The public key (FIO5nambcL1f7ot8yJTsf3zfPkSpeAB4JBE4qWPUdJbCWQJpXEUiy), account (qcic4ydb3vqh) has a registered address (proxy@greymass), and is also registered as a voting proxy.

[adsorptionenthalpy]

Seeing the same thing using our internal tooling.

I submitted a transaction for regaddress which included a tpid on mainnet, and the table within fio.tpid remained empty.

The public key (FIO5nambcL1f7ot8yJTsf3zfPkSpeAB4JBE4qWPUdJbCWQJpXEUiy), account (qcic4ydb3vqh) has a registered address (proxy@greymass), and is also registered as a voting proxy.

In this instance, tpid should be in the address@domain format. There is a FIO public key in the field.
Important to note that this is supposed to act passively so the rest of the transaction can succeed.... so you will not get an error.

[aaroncox]

That was my particular problem - using a FIO Address did actually create the record in the fio.tpid table. The corrected transaction is here, which created the table entry.

I'll continue to monitor the table as development continues to see if I can identify any other calls that may not be working, but regaddress appears to work.