bridge.yaml
E ValueError: Protocol scaffolding failed: Error: Protocol is NOT generated. The following error happened while generating the protocol:
E Error while parsing the protocol specification: Content 'initialisation_tx_hash' with type 'pt:optional[pt:str]' under performative 'bridge' is already defined under performative 'initialise_claim' with a different type ('pt:str').
cross_chain_arbitrage.yaml
E aea.configurations.base.ProtocolSpecificationParseError: Extra protobuf code snippet provided. Type 'ct:ArbitrageResultCode' is not used anywhere in your protocol definition.
default
Already present in dummy_agent_tim since you're using eightballer/base as a template.
order_book
has issue where protocol_specification_id does not match the name of the spec file (here, also noted in PR #634 )
Originally posted by @Karrenbelt in 8ball030/auto_dev#618 (comment)
bridge.yamlcross_chain_arbitrage.yamldefaultAlready present in
dummy_agent_timsince you're usingeightballer/baseas a template.order_bookhas issue where
protocol_specification_iddoes not match the name of the spec file (here, also noted in PR #634 )Originally posted by @Karrenbelt in 8ball030/auto_dev#618 (comment)