Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create 0141-remote-onchain-execution.md #141

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

EmelyanenkoK
Copy link
Member

No description provided.


# Summary

This TEP proposes a way of how one contract may execute code (including get nethods) or read data of other contracts in asynchronous manner. Note: data may and often will become outdated during delivery and it MUST to be taken into account dduring protocol ddevelopment.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

during

@mr-tron
Copy link

mr-tron commented Jan 23, 2024

I don't understand why are you want to use all three flags (ihr, bounce, bounced) if you need only first. less changes in schemes.

@mr-tron
Copy link

mr-tron commented Jan 23, 2024

also not all messages in the past has flag ihr_disabled = true

select ihr_disabled, msg_type, count(1)  from blockchain.messages group by ihr_disabled, msg_type
+------------+---------+---------+
|ihr_disabled|msg_type |count    |
+------------+---------+---------+
|false       |ExtInMsg |53448826 |
|false       |ExtOutMsg|1923844  |
|false       |IntMsg   |3417621  |
|true        |IntMsg   |248430531|
+------------+---------+---------+

so we will need to parse old messages with one scheme and new with another based on additional context information

@mr-tron
Copy link

mr-tron commented Jan 23, 2024

select ihr_disabled, bounce,bounced,  count(1)  from blockchain.messages where msg_type = 'IntMsg' group by ihr_disabled, bounce, bounced
+------------+------+-------+---------+
|ihr_disabled|bounce|bounced|count    |
+------------+------+-------+---------+
|false       |false |false  |1586934  |
|false       |true  |false  |1830692  |
|true        |false |false  |71614077 |
|true        |false |true   |1999833  |
|true        |true  |false  |174818024|
+------------+------+-------+---------+


// We keep it to be able to parse history
int_msg_info_ihr_usual$0010 _:CommonInternalMsgInfo = CommonMsgInfo;
int_msg_info_ihr_no_bounce$0000 _:CommonInternalMsgInfo = CommonMsgInfo;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about ..._ihr_bounced$0001? That case is not possible?

```


Now we "freed" `0111` prefix space and can use it for new types of internal messages, for instance

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Theoretically, prefix 0011 is also not possible (ihr + bounce + bounced).


# Summary

This TEP proposes a way of how one contract may execute code (including get nethods) or read data of other contracts in asynchronous manner. Note: data may and often will become outdated during delivery and it MUST to be taken into account dduring protocol ddevelopment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"get nethods", "dduring", "ddevelopment" 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants