bitjson bch-vm-limits issues

bitjson / bch-vm-limits

Retargets limits to make Bitcoin Cash contracts more useful and reduce compute requirements for nodes.

4 stars 4 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Recommendation from GP to help this CHIP reach minimum viability

#30 emergent-reasons opened 2 days ago
0
explicitly note source of magic numbers in Hashing Limit section

#29 emergent-reasons opened 5 days ago
1
add consideration of static vs (static + dynamic) cost accounting

#28 emergent-reasons opened 5 days ago
1
fix truncation and precision ambiguities in javascript examples

#27 emergent-reasons opened 5 days ago
0
fix js operation cost limit

#26 emergent-reasons closed 5 days ago
2
Correct cost for `OP_*VERIFY`

#25 bitjson closed 1 week ago
2
Update readme.md -- hash digest iteration table has an error

#24 cculianu closed 2 weeks ago
1
Please update "Technical Overview of Changes to C++ Clients"

#23 cculianu closed 5 days ago
0
p2sh is 2 or more iters, not exactly 3

#22 cculianu closed 2 weeks ago
1
Base densities in input length rather than transaction length

#21 bitjson closed 2 weeks ago
0
Include numeric encoding in operation costs

#20 bitjson closed 2 weeks ago
0
add emphasis on density, add section to rationale

#19 A60AB5450353F40E opened 2 weeks ago
2
side-effect of limiting density

#18 A60AB5450353F40E opened 2 weeks ago
5
Correct and clarify operation cost table

#17 bitjson closed 1 month ago
0
Count all hashing ops against the hashing limit (don't exclude CHECKSIG)

#16 A60AB5450353F40E closed 1 month ago
4
The 130kb limit rule should not be created, it is too arbitary.

#15 tomFlowee closed 1 month ago
8
How are hashing ops limits applied in the case of p2sh?

#14 cculianu closed 1 month ago
1
Specification should specify at what point during execution the stack memory usage limit is enforced

#13 cculianu closed 1 month ago
2
Stack memory usage limit should count size of both the primary and "alt" stack

#12 cculianu closed 1 month ago
1
Should we limit the depth of the evaluation stack?

#11 bitjson closed 1 month ago
2
Can the stack memory usage limit be improved?

#10 bitjson closed 1 month ago
8
Replace `SigChecks` with a limitation on `OP_CODESEPARATOR`?

#9 bitjson closed 1 month ago
1
Density-based limits

#8 bitjson closed 1 month ago
9
Benchmark VMB tests

#7 bitjson opened 7 months ago
2
Propose for 2025 upgrade

#6 bitjson closed 7 months ago
0
TODO: optimize performance benchmarks

#5 bitjson closed 7 months ago
1
Drop stack memory usage limit, leave 520 byte push limit

#4 bitjson closed 7 months ago
1
Protection against unknown vectors

#3 monsterbitar closed 7 months ago
2
Attack in a single TX vs over multiple TXs?

#2 monsterbitar closed 3 years ago
1
OP_CODESEPARATOR

#1 monsterbitar closed 3 years ago
2