docs: update smart contracts async flow diagram

[VolodymyrBg]

Proposed changes

1. Updated the smart_contracts_async_flow.svg diagram in the custom contracts tutorial to:

• Add the Blockchain Connector component to accurately represent the architecture
• Improve the flow visualization with more detailed steps
• Add color coding for better visual distinction between components
• Include a note about event subscription options
• Make the diagram more comprehensive and modern

2. Removed the TODO comment from the custom_contracts/index.md file

Fixes # <issue_number_here>

---

Types of changes

• Bug fix
• New feature added
• Documentation Update

---

Please make sure to follow these points

• I have read the contributing guidelines.
• I have performed a self-review of my own code or work.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generates no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• My changes have sufficient code coverage (unit, integration, e2e tests).

---

Screenshots (If Applicable)

---

Other Information

The previous diagram was simplified and didn't accurately represent the role of the Blockchain Connector or the complete flow of events. This update provides a more accurate and detailed representation of how custom contract interactions work in FireFly, which will help developers better understand the asynchronous nature of blockchain transactions.

[EnriqueL8]

Thanks @VolodymyrBg this is super useful, it seems that the SVG is cut and I can't see the store events flow and emit events to the App, could you please add that?

[VolodymyrBg]

@EnriqueL8 LIKE THIS?

[EnriqueL8]

Thanks , looking better! A few changes needed please

[VolodymyrBg]

@EnriqueL8 Corrected. I can squash commits if it's necessary, cause too many of them. Sorry for mess

[EnriqueL8]

No worries, could you squash please :)

[VolodymyrBg]

@EnriqueL8 Done

[EnriqueL8]

Sorry for spotting this later in the review

[EnriqueL8]

After reviewing the code flow and where the TODO was, this diagram doesn't show the Async behavior of a smart contract invoke. The blockchain connector will return a transaction accepted before it's submitted to the blockchain and the response of the operation being completed is a receipt from the blockchain so two things need changing:

• Transaction accepted from connector to FireFly should just after the Submit Transaction
• Before the emit blockchain events there is also a Retrieve receipt/confirmation for TX and then confirm tx to FireFly. At this point the operation is updated.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.95%. Comparing base (71f04f3) to head (72abbe0).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1661   +/-   ##
=======================================
  Coverage   99.95%   99.95%           
=======================================
  Files         339      339           
  Lines       29780    29780           
=======================================
  Hits        29768    29768           
  Misses          8        8           
  Partials        4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.