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

JSON-RPC method to find transactions in initial OMNI (MSC) crowdsale #1277

Open
msgilligan opened this issue Nov 8, 2022 · 2 comments
Open

Comments

@msgilligan
Copy link
Member

msgilligan commented Nov 8, 2022

Although Omni Core is able to find transactions from the initial OMNI (MSC) crowdsale and uses them to compute OMNI balances of participating addresses, there appears to be no JSON-RPC method that returns these transactions. omni_getcrowdsale would be a likely candidate, but omni_getcrowdsale 1 true returns: No information available about transaction.

omni_getcrowdsale returns an array named participanttransactions which contains the following information for each transaction for other crowdsales (e.g. MAIDSAFE omni_getcrowdsale 3 true):

{
    "txid" : "4ec15360a03d23c069c2fd4a035cfee28af5ddfdd5a6839934dd2629129d477e",
    "amountsent" : "100.00000000",
    "participanttokens" : "485781",
    "issuertokens" : "0"
}

I propose the following two enhancements:

A. Extend the existing omni_getcrowdsale method to support propertyid 1.
B. Add blocktime and sendingaddress to each transaction object in participanttransactions

I'm not sure if the initial crowdsale exactly maps into the return object for omni_getcrowdsale (e.g. closetx doesn't apply) but it is probably close enough.

@msgilligan
Copy link
Member Author

Note: TOMNI were also awarded, so this applies to propertyid 2 as well.

@srbaeza-ai
Copy link

#1277

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

No branches or pull requests

2 participants