🔨

docs/core/core-geth.md

@@ -18,6 +18,7 @@ approaches the EVM-based protocols as technology that can -- and should -- be ge
 - Available `trace_block` and `trace_transaction` RPC API congruent to the OpenEthereum API (including a 1000x performance improvement vs. go-ethereum's `trace_transaction` in some cases).
 - Available `debug_removeTransaction` API method.
 - Comprehensive service discovery with OpenRPC at `rpc.discover`.
+- `debug_removeTransaction`
 
 #### Comprehensive RPC API Service Discovery
 
@@ -78,3 +79,17 @@ and intended_ to support one chain: _Ethereum_. From this perspective, configura
     + ECIP1014 (defuse difficulty bomb), etc. :wink:
 - Out-of-the-box support for Ethereum Classic, EtherSocial, Social, and MIX networks.
 
+### Limitations
+
+Things ethereum/go-ethereum can or will do that CoreGeth won't, or doesn't by default.
+
+- A huge and diverse number of default pipeline-delivered build targets.
+  This is a defaults and configuration sanity challenge for CoreGeth. We're vastly outnumbered by ethereum/go-ethereum maintainers
+  and contributors, and ensuring proper delivery of a whole bunch of diverse artifacts is beyond our capacity.
+  With that said, just because CoreGeth doesn't provide artifacts for a given architecture or OS doesn't mean it can't. 
+  If ethereum/go-ethereum can build and package for it, then with some elbow grease, CoreGeth can too.
+- The `puppeth` CLI program has been [removed](https://github.com/etclabscore/core-geth/pull/270). This is a "wizard"-style interactive program that helps beginners
+  configure chain and network settings.
+- Trim absolute file paths during build. As of a [somewhat-recent](TODO) Go version, `go build` provides a `-trim` flag
+  which reduces the size of the binaries and anonymizes the build environment. This was removed because stripping file paths
+  caused automatic service discovery features to break (they depend, in part, on source file path availability for build-time AST and runtime reflection).