chore: update txn build opt for compatible with older aptos node

[Haupc]

Description

Aptos now support NoAccountSignature in simulation for fee payer and multi agent transaction. But it's only supported on node version >= 1.19.1. I add an old way to simulate using public key of fee payer to construct authenticator with zero signature. It would support more wide range of aptos node versions.

Related Links

• Release node
• PR that support NoAccountSignature
• Aptos TS SDK reference still use public key if provided.

[gregnazario]

Description

Aptos now support NoAccountSignature in simulation for fee payer and multi agent transaction. But it's only supported on node version >= 1.19.1. I add an old way to simulate using public key of fee payer to construct authenticator with zero signature. It would support more wide range of aptos node versions.

Related Links

• Release node
• PR that support NoAccountSignature
• Aptos TS SDK reference still use public key if provided.

Interesting... is anyone running a node version < 1.19.1?

Aptos is on 1.30... something right now

[Haupc]

Description

Aptos now support NoAccountSignature in simulation for fee payer and multi agent transaction. But it's only supported on node version >= 1.19.1. I add an old way to simulate using public key of fee payer to construct authenticator with zero signature. It would support more wide range of aptos node versions.

Related Links

• Release node
• PR that support NoAccountSignature
• Aptos TS SDK reference still use public key if provided.

Interesting... is anyone running a node version < 1.19.1?

Aptos is on 1.30... something right now

I'm not sure about is is anyone running a node version < 1.19.1 now.

But I think that backward compatibility isn't just for current users - it's for attracting new developers who are building on forks or derivative projects. Supporting them grows our ecosystem and brings in more contributors who might otherwise choose a different foundation. I can see the movement chain is using a quite low version of aptos. In the future it could be more and more chains like that. We keep the sdk compatible with all of them will make Aptos move ecosystem strong and engage more builders

[Haupc]

@gregnazario please take a look

[gregnazario]

Description

Aptos now support NoAccountSignature in simulation for fee payer and multi agent transaction. But it's only supported on node version >= 1.19.1. I add an old way to simulate using public key of fee payer to construct authenticator with zero signature. It would support more wide range of aptos node versions.

Related Links

• Release node
• PR that support NoAccountSignature
• Aptos TS SDK reference still use public key if provided.

Interesting... is anyone running a node version < 1.19.1?
Aptos is on 1.30... something right now

I'm not sure about is is anyone running a node version < 1.19.1 now.

But I think that backward compatibility isn't just for current users - it's for attracting new developers who are building on forks or derivative projects. Supporting them grows our ecosystem and brings in more contributors who might otherwise choose a different foundation. I can see the movement chain is using a quite low version of aptos. In the future it could be more and more chains like that. We keep the sdk compatible with all of them will make Aptos move ecosystem strong and engage more builders

Unfortunately, we don't support derivatives. Not using a public key is much more adaptable. Derivatives are welcome to build their own SDK forks as well.