Zeph Grunschlag

## Problem `min-balance` is available in `algod` but not in the JS SDK. ## Solution https://github.com/algorand/go-algorand/pull/3287 has introduced `min-balance` to the response of `algod`'s `/v2/accounts/{{ACCOUNT}}` as well as to the...

More Efficient Scratch Slot Assignments in the ABI-Router

3

## Problem Consider this [PyTEAL generated approval program](https://github.com/algorand/graviton/blob/5ed03a38db14ae2c50f5e8d5d582096c56992dc5/tests/teal/router/questionable.teal#L266-L317) with companion [ABI contract](https://github.com/algorand/graviton/blob/5ed03a38db14ae2c50f5e8d5d582096c56992dc5/tests/teal/router/questionable.json). It came from this [PyTEAL compiler test](https://github.com/algorand/pyteal/blob/feature/abi/pyteal/compiler/compiler_test.py#L2198). It specifies several methods. In particular, it defines methods `sub(uint64,uint64)uint64` and...

WIP: TEAL to PyTEAL Source Mapper

1

# Source Map ## Example PyTeal ```python @Subroutine(TealType.none) def swap(x: ScratchVar, y: ScratchVar): z = ScratchVar(TealType.anytype) return Seq( z.store(x.load()), x.store(y.load()), y.store(z.load()), ) @Subroutine(TealType.none) def cat(x, y): return Pop(Concat(x, y)) def...

## Problem When a user creates a `DynamicScratchVar`, the compiler -by design- does not block-off slot space for this variable. Typically, the compiler allocates scratch slots at runtime with slot...

## Problem Usage of ABI subroutines is more verbose than necessary. For example, consider these 2 cases: ```python Int65 = Tuple2[Bool, Uint64] @ABIReturnSubroutine def int65_negate(x: Int65, *, output: Int65): x0...

## Problem We've recently started testing some of our RST doc snippets in the file `tests/integration/user_guide_test.py`. Though testing is much preferred over no testing the main problem is that there...

Quasi-bug: TEAL Output is Unstable

2

# TEAL Output Should be Stable When No Changes are Made to the Actual Compilation ## Why is this useful This would allow us to have less flaky end-to-end tests...

# Just a stub at this point... following up on [retro promise](https://algorand.atlassian.net/wiki/spaces/SCY/pages/2347892761/Scytale+Retro+02+16+2022)

Better visibility while debugging by adding `__str__` methods to classes

1

## Problem When I compile a PyTeal program into TEAL, it would be nice to easily introspect information about objects in case a problem occurs or in the case that...