bug: integration test throws warnings for each transaction: Service account does not contain a service challenge

[smuu]

WARN prism_prover::prover > Failed to process transaction: Transaction { id: "6@gmail.com", operation: CreateAccount { id: "6@gmail.com", service_id: "test_service", challenge: Signed(Ed25519(Signature { R_bytes: "c3c398b3f9b6fb2a9baae6d0b3623f32c004806656176092e8a0a0021042d509", s_bytes: "e81ebe79a50a41dffc622cf793d894af72dd4054fe84b57b9bdbbd96251a1501" })), key: Ed25519(VerificationKey("a149cf2036bf78dfeb32b8e3201af1df24339e07efad9f83430644f8d417ec13")) }, nonce: 0, signature: Ed25519(Signature { R_bytes: "26211f99939e6ca2f628b76faa5b21a06b62e5efb52958867b68ad6ca3ecd276", s_bytes: "8cdd5df27302a0371b49d24821ad72ae90cec33100606949699d59ccbd3b7907" }), vk: Ed25519(VerificationKey("a149cf2036bf78dfeb32b8e3201af1df24339e07efad9f83430644f8d417ec13")) }. Error: Service account does not contain a service challenge

[distractedm1nd]

I believe this is caused by a bug in rocksdb actually, which is fixed in #189

[jns-ps]

My theory is:

• Is it possible that the accounts field in TransactionBuilder is never updated?
• As a result, let acc = self.builder.accounts.entry(self.transaction.id.clone()).or_default(); would always take the "or_default" route when creating "RegisterService" Transactions
• And then you'd end up with an invalid transaction on the DA layer (because the default for Account is probably service_challenge = None)