8000 We should limit the moves per tx · Issue #133 · dustproject/dust · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
/ dust Public

We should limit the moves per tx #133

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.

Sign up for GitHub

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

8000
Jump to bottom
Open
dhvanipa opened this issue Mar 19, 2025 · 2 comments
Open

We should limit the moves per tx #133

dhvanipa opened this issue Mar 19, 2025 · 2 comments

Comments

@dhvanipa
Copy link
Member

Right now there's no limit
@alvrs
Copy link
Contributor
alvrs commented Mar 19, 2025

Also should limit distance per time, so probably per block. Either a hard limit on speed, or scale the energy cost to make it infeasible to walk faster than the sprinting limit

@frolic
Copy link
Contributor
frolic commented Mar 19, 2025 •
edited
Loading

"moves per tx" as in the number of moves jammed into whatever the batchCall interval is? couldn't we collapse all sequential move requests to just be the last one?

for example

  • move to 5,6
  • move to 6,6
  • move to 6,7
  • mine
  • move to 6,6

could be collapsed to

  • move to 6,7
  • mine
  • move to 6,6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@frolic @dhvanipa @alvrs
0