pull down to refresh

227 sats \ 2 replies \ @optimism 20 Aug \ on: One thing L402 can learn from x402 AI bitcoin lightning

Since it only supports 2 corpochains, the "well-funded" part is clear, as well as where the funding came from.

I wonder though: Is it really a good idea to make your frontmost app layer security service (the WAF) a payment gateway?

PS: does opti see static accounts? So cool! Now I just pay you once and then can see all your customers, lmao. What a shitshow.

{
  "MonetizationConfig": {
    "CryptoConfig": {
      "PaymentNetworks": [
        {
          "Chain": "BASE",
          "WalletAddress": "0x1234567890abcdef1234567890abcdef12345678",
          "Prices": [
            {
              "Amount": "0.001",
              "Currency": "USDC"
            }
          ]
        },
        {
          "Chain": "SOLANA",
          "WalletAddress": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU",
          "Prices": [
            {
              "Amount": "0.001",
              "Currency": "USDC"
            }
          ]
        }
      ]
    }
  }
}
write
compose
133 sats \ 1 reply \ @k00b OP 21 Aug
Is it really a good idea to make your frontmost app layer security service (the WAF) a payment gateway?

Good point. WAF does have label forwarding via headers so placing the payment gateway downstream should be straightforward. Perhaps that's even how they've implemented it and are just mixing concerns at the product level.

reply
107 sats \ 0 replies \ @optimism 21 Aug
Perhaps that's even how they've implemented it and are just mixing concerns at the product level.

Yeah I was thinking about that after the timer expired and it could be just a route hint that opaquely sits together with config at the WAF because for some reason Amazon didn't want to create yet another AWS product (first time ever tho, lol!)

reply