bitjson/bch-vm-limits issues and pull requests

#41 - Add Amagi Wallet and Amagi Finance support

Pull Request - State: closed - Opened by Amagi-Finance 3 months ago

#40 - Add rbch and CashFusion Red Team support

Pull Request - State: closed - Opened by Rucknium 3 months ago - 1 comment

#39 - Correct list of operations with numeric outputs

Issue - State: closed - Opened by bitjson 4 months ago

#38 - Clarify costing of signing serialization hashing

Issue - State: closed - Opened by bitjson 4 months ago

#38 - Clarify costing of signing serialization hashing

Issue - State: closed - Opened by bitjson 4 months ago

#37 - Stakeholder response from `Flowee`

Issue - State: closed - Opened by tomFlowee 4 months ago - 10 comments

#37 - Stakeholder response from `Flowee`

Issue - State: closed - Opened by tomFlowee 4 months ago - 10 comments

#36 - Patch 1

Pull Request - State: closed - Opened by 2qx 4 months ago - 1 comment

#35 - Add feedback by Melroy

Pull Request - State: closed - Opened by melroy89 4 months ago - 5 comments

#35 - Add feedback by Melroy

Pull Request - State: closed - Opened by melroy89 4 months ago - 5 comments

#34 - Unjumble words

Pull Request - State: closed - Opened by bitjson 5 months ago

#34 - Unjumble words

Pull Request - State: closed - Opened by bitjson 5 months ago

#33 - Also disable manpage build

Pull Request - State: closed - Opened by melroy89 5 months ago - 1 comment

#32 - Fix order of execution

Pull Request - State: closed - Opened by melroy89 5 months ago

#31 - Finalize CHIP language and rationale, prepare for stakeholder statements

Pull Request - State: closed - Opened by bitjson 5 months ago

#30 - Recommendation from GP to help this CHIP reach minimum viability

Issue - State: closed - Opened by emergent-reasons 5 months ago - 3 comments

#30 - Recommendation from GP to help this CHIP reach minimum viability

Issue - State: closed - Opened by emergent-reasons 5 months ago - 3 comments

#29 - explicitly note source of magic numbers in Hashing Limit section

Issue - State: closed - Opened by emergent-reasons 6 months ago - 3 comments

#29 - explicitly note source of magic numbers in Hashing Limit section

Issue - State: closed - Opened by emergent-reasons 6 months ago - 3 comments

#28 - add consideration of static vs (static + dynamic) cost accounting

Issue - State: closed - Opened by emergent-reasons 6 months ago - 3 comments

#28 - add consideration of static vs (static + dynamic) cost accounting

Issue - State: closed - Opened by emergent-reasons 6 months ago - 3 comments

#27 - fix truncation and precision ambiguities in javascript examples

Pull Request - State: closed - Opened by emergent-reasons 6 months ago - 1 comment

#26 - fix js operation cost limit

Pull Request - State: closed - Opened by emergent-reasons 6 months ago - 2 comments

#25 - Correct cost for `OP_*VERIFY`

Issue - State: closed - Opened by bitjson 6 months ago - 2 comments

#24 - Update readme.md -- hash digest iteration table has an error

Pull Request - State: closed - Opened by cculianu 6 months ago - 1 comment

#23 - Please update "Technical Overview of Changes to C++ Clients"

Issue - State: closed - Opened by cculianu 6 months ago

#22 - p2sh is 2 or more iters, not exactly 3

Pull Request - State: closed - Opened by cculianu 6 months ago - 1 comment

#21 - Base densities in input length rather than transaction length

Issue - State: closed - Opened by bitjson 6 months ago

#20 - Include numeric encoding in operation costs

Issue - State: closed - Opened by bitjson 6 months ago

#19 - add emphasis on density, add section to rationale

Pull Request - State: closed - Opened by A60AB5450353F40E 6 months ago - 3 comments

#18 - side-effect of limiting density

Issue - State: closed - Opened by A60AB5450353F40E 6 months ago - 9 comments

#17 - Correct and clarify operation cost table

Issue - State: closed - Opened by bitjson 6 months ago

#16 - Count all hashing ops against the hashing limit (don't exclude CHECKSIG)

Issue - State: closed - Opened by A60AB5450353F40E 10 months ago - 4 comments

#15 - The 130kb limit rule should not be created, it is too arbitary.

Issue - State: closed - Opened by tomFlowee 11 months ago - 8 comments

#14 - How are hashing ops limits applied in the case of p2sh?

Issue - State: closed - Opened by cculianu 11 months ago - 1 comment

#13 - Specification should specify at what point during execution the stack memory usage limit is enforced

Issue - State: closed - Opened by cculianu 11 months ago - 2 comments

#12 - Stack memory usage limit should count size of both the primary and "alt" stack

Issue - State: closed - Opened by cculianu 11 months ago - 1 comment

#11 - Should we limit the depth of the evaluation stack?

Issue - State: closed - Opened by bitjson about 1 year ago - 2 comments

#10 - Can the stack memory usage limit be improved?

Issue - State: closed - Opened by bitjson about 1 year ago - 8 comments

#9 - Replace `SigChecks` with a limitation on `OP_CODESEPARATOR`?

Issue - State: closed - Opened by bitjson about 1 year ago - 1 comment

#8 - Density-based limits

Issue - State: closed - Opened by bitjson about 1 year ago - 9 comments

#7 - Benchmark VMB tests

Issue - State: closed - Opened by bitjson about 1 year ago - 3 comments

#6 - Propose for 2025 upgrade

Pull Request - State: closed - Opened by bitjson about 1 year ago

#5 - TODO: optimize performance benchmarks

Issue - State: closed - Opened by bitjson almost 3 years ago - 1 comment

#4 - Drop stack memory usage limit, leave 520 byte push limit

Issue - State: closed - Opened by bitjson almost 3 years ago - 1 comment

#3 - Protection against unknown vectors

Issue - State: closed - Opened by monsterbitar almost 4 years ago - 2 comments

#2 - Attack in a single TX vs over multiple TXs?

Issue - State: closed - Opened by monsterbitar almost 4 years ago - 1 comment

#1 - OP_CODESEPARATOR

Issue - State: closed - Opened by monsterbitar almost 4 years ago - 2 comments

GitHub / bitjson/bch-vm-limits issues and pull requests