Followin LogoFollowin
  • icon of HOMEicon of HOME
    Today
  • icon of INTELicon of INTEL
    Intel
  • icon of EXPLOREicon of EXPLORE
    Market
  • icon of EARNicon of EARN
    Earn
  • icon of SETTINGicon of SETTING
    Settings
    • Account
    • Theme Selection
      • Light
      • Dark
    • Language
      • English
      • 简体中文
      • 繁體中文
      • Tiếng Việt
      • 한국어
Followin APP
Mine Web3 Possibilities
avatar
Log in
avatar
Portland.HODL
3,526 Twitter followers
Follow
#Bitcoin - custom btc core .23 node operator & contributor - programming - self taught maker
Posts
avatar
Portland.HODL
11-12
After deeper reflection, I am abandoning any work on my >=520 byte ScriptPubkey proposal as the confiscatory risk of chained presigned transactions is non-zero. Also I oppose temporary softforks which are an anesthetic for the pain consensus building.
avatar
Portland.HODL
10-09
x.com/PortlandHODL/status/1973...… My take on this. Move the bar to consensus and fix DoS Blocks in the process.
Portland.HODL | 520 Byte ScriptPubkeys
@PortlandHODL
10-03
Just did a thing ... Proposal: Limit ScriptPubkey to be less than <= 520 bytes at the consensus level. Solves: - DoS Blocks - Large OP_RETURNs Would love to hear from others why this can or won't work. https://groups.google.com/g/bitcoindev/c/YO8ZwnG_ISs…
avatar
Portland.HODL
09-10
Yesterday there was an antivirus (av) test vector placed into an OP_RETURN. This isn't a virus but instead a string to test if an AV software is working. Trying to create a knowledge share here. So if your node triggered your av, could you share some details?
TST
2.76%
-- END --