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

Rename type Ledger to Slot #277

Closed
b-yap opened this issue Feb 27, 2023 · 6 comments
Closed

Rename type Ledger to Slot #277

b-yap opened this issue Feb 27, 2023 · 6 comments
Assignees
Labels
type:chore Maintenance tasks

Comments

@b-yap
Copy link
Contributor

b-yap commented Feb 27, 2023

As mentioned by @ebma :

While 'Ledger' is used to describe a block in the Stellar world, the term 'slot' is rather used in the SCP consensus paper etc. But at the end of the day it boils down to the same thing when it comes to the number we store for a ledger and a slot. For one transaction x the slot and ledger will be equal to each other.

Thus, I would prefer if we find a better way for describing this. If I remember correctly we already have a type for Slot, maybe we could just re-use that one.

@b-yap
Copy link
Contributor Author

b-yap commented Feb 27, 2023

@ebma
While I'm all about Slot == Ledger, there's a difference of datatypes.

Slot is defined as u64:

pub type Slot = Uint64;

and Ledger is u32:

pub type Ledger = u32;

Shall we address where to handle the conversion from Ledger to Slot? And also, where to define the Slot type to make it easily accessible?

Can we actually cleanup the following:


'Ledger' is used to describe a block in the Stellar world,

  • Is it correct to assume, that the 'Ledger' term will strictly be used only when interacting with the stellar-substrate-sdk lib?

the term 'slot' is rather used in the SCP consensus paper

  • Is it correct to assume, that the 'Slot' term will strictly be used only when interacting with the stellar-relay-lib crate?

@vadaynujra
Copy link

Hey team! Please add your planning poker estimate with Zenhub @ebma @b-yap @ashneverdawn

@b-yap b-yap self-assigned this Oct 11, 2023
@prayagd
Copy link
Collaborator

prayagd commented Dec 7, 2023

@b-yap can i icebox this if not urgent?

@TorstenStueber
Copy link
Contributor

(also @ebma: still relevant?)

@ebma
Copy link
Member

ebma commented Dec 19, 2023

This is just some minor refactoring and not super urgent. I'd say it's fine to move it to the icebox but not close it.

@TorstenStueber
Copy link
Contributor

Okay, moved to Icebox.

@TorstenStueber TorstenStueber added type:chore Maintenance tasks and removed priority:low Do it some day labels Dec 23, 2023
b-yap added a commit that referenced this issue Feb 23, 2024
b-yap added a commit that referenced this issue Feb 23, 2024
b-yap added a commit that referenced this issue Feb 26, 2024
* first iteration

* cleanup more todo's

* cleanup txsets todos

* interlay/interbtc-clients@622f36b

* fix #417 (comment)

* cleanup is_public_network() method
and the testchain runtime cfg-if

* implement the faucet_url todo

* is_transaction_already_submitted

* 2nd iteration to improve is_transaction_already_submitted()

* revert changes of the `fn is_transaction_already_submitted()`

* test prepush-hook

* update `fn is_transaction_already_submitted()`

* remove unnecessary files

* fix resources

* fix check_bump_sequence_number_and_submit() test case;

update the configs

* just allow it

* cleanup the comments

* clippy cleanup

* #277 and #486 (comment),
#486 (comment)

* rebase and #486 (comment)

* rename file for stellar_secretkey_testnet

* update function `get_mainnet_secret_key` to `get_secret_key` that accepts 2 params

* clippy fix

* Update Cargo.lock

update cargo lock
@b-yap b-yap closed this as completed Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:chore Maintenance tasks
Projects
None yet
Development

No branches or pull requests

5 participants