Highlights
- Arctic Code Vault Contributor
- Developer Program Member
Pinned
2,584 contributions in the last year
Contribution activity
December 2020
Created 202 commits in 3 repositories
Created a pull request in blockstack/stacks-blockchain that received 2 comments
Opened 15 other pull requests in 1 repository
blockstack/stacks-blockchain
2
open
13
merged
- Fix (append ...) documentation
- Release Xenon
- Developer / Miner Experience: improving logs
- PoX - Adjustments
- Atlas & BNS: Garbage collection, BNS constants + BNS genesis data
- Add lockup events
- Test: add coverage for genesis consistency
- Next
- BNS: read-only method for name prices
- Mainnet compatibility fixes
- Clarity: additional token functions
- Clarity: Static failures for unchecked results
- Clarity: variadic map function
- Clarity: introduce merge function
- Clarity: enhancing tuples - volume 1
Reviewed 25 pull requests in 2 repositories
blockstack/stacks-blockchain 24 pull requests
- Update Xenon magic bytes for reset
- Remove PoX state from consideration when validating prepare-phase sortitions
- Update cost-voting to use block-height over burn-block-height
- Address #2224 -- separate initial rewards start from first block height
- MARF RAM Improvement
- Fix clarity-js-sdk commit message
- Clarity DB Fixes
- Release `next` to `master`: non-consensus breaking
- Implement transaction fees
- Commit window fixes
- Feat/pob prepare phase
- Cost Voting Contract Integration
- fix: `mstx_balance` to `ustx_balance` in tomls and readmes
- Inconsistent mempool admission: #2050, #1719
- Transfer STX via On-Bitcoin Operations
- Xenon Magic Bytes
- Clarity Conveniences: `let*`, `element-at`, `contains`
- Coinbase schedule and paying-forward
- Fix/marf 1294
- Microblock fork-handling and basic mining
- Fix/2108
- Cost-tracking: #2042, intercepting contract-call costs
- Merge `next-costs` into `next`
- Fix: #2097, event dispatcher should not unpack response results
blockstack/stacks-wallet 1 pull request
Created an issue in clarity-lang/reference that received 6 comments
Rename print to event
Events are a really convenient mechanism implemented via (print). As a smart contract developer, when discovering the documentation, it's not obvio…
6
comments