Describe the bug
In VerifyFullExitNftTx function, there is no match logic between tx.CreatorAccountIndex and tx. CreatorAccountNameHash. tx.CreatorAccountIndex and tx. CreatorAccountNameHash are parts of pubData, and used in L1 smart contract. If the match logic is missing, then it's possible for l2 give an invalid tx.CreatorAccountIndex.

To Reproduce
Suppose committer is malicious
Committer force to assign an invalid account index to tx.CreatorAccountIndex

Expected behavior
The match logic is removed by #24, we should add it back, and in zkbnb repository, we should modify FullExitNft tx details generation logic

Describe the bug
When there are empty txs, block circuits ignore doing state root verification, the code:

isEmptyTx := api.IsZero(api.Sub(block.Txs[block.TxsCount-1].TxType, std.TxTypeEmptyTx))
notEmptyTx := api.IsZero(isEmptyTx)
std.IsVariableEqual(api, notEmptyTx, block.NewStateRoot, block.Txs[block.TxsCount-1].StateRootAfter)

So if malicious prover gave a wrong block.NewStateRoot in the block which contains empty txs, the circuit will also passed.

To Reproduce
Malicious prover gave a wrong block.NewStateRoot in the block which contains empty txs

Expected behavior
The block circuit should guarantee that block.NewStateRoot is correctly constructed by all txs.

Additional context
zkbnb repository should make changes for empty txs, see bnb-chain/zkbnb#203