Web appOpen in Telegram
BBeam Developers Support

Beam Developers Support

@beamdevsupport · group · Tech · indexed since 2026-07-25
209members
2writing in 30 days
8messages in 30 days
11 104messages in the index
  1. H
    thanks, the manifest checks out this exact package installs and runs on the official desktop wallet, and all my prior versions had the same api values and file layout (never had a fonts folder). the failure is upstream of validation, the package bytes can't be fetched at all, which is why max's endpoint 504s on the raw CID too. once a publicly reachable node pins it (the file's on my github releases), installs should come back everywhere
Whole thread · 1 reply →
  1. H
    confirmed, a fresh node now pulls the CID in seconds, you've ended a outage with that pin, your node is currently the only public seed so that pin is load bearing, much appreciated if it stays. one leftover PriviMW still spins on the install (repro'd on my own phone, fresh wallet, wifi and 4G, other dapps fine), but plain go-ipfs fetches instantly, so that one's an app bug for @PriviMW, not your side.
  2. H
    your fix hit the http endpoint but not the swarm, wallets fetch p2p so installs still fail. you have the right file on that box, can you ipfs add and pin it in your swarm node?
      1. H
        from your node, right, but the swarm side can't pull it, fresh node in the mainnet swarm (psk fingerprint 845a79...) times out on that CID unless my own desktop is open. what's your node's peer id and swarm address? I'll try it from here, guessing either different swarm or your announce addr
          1. H
            that's the thing, they can't ask you, your provider record shows in the DHT (12D3Koo..., that you?) but findpeer on it returns routing not found, so fetchers can't resolve you to an address. can you send your node's peer id and public swarm address (ip:port)? I'll dial it directly from a fresh node here, if the direct connect plus fetch works, it's just your announce config, one line fix
              1. H
                found it.... your dial address times out from outside, tcp to 159.69.148.122:10100 won't connect, host answers on other ports so it looks like the firewall isn't allowing 10100 through. open it and I'll confirm the fetch within a minute. lets us know, thanks by the way
                  1. H
                    confirmed direct dial connects and the fetch pulls the full package, correct hash, from a fresh node that only knows your address. that firewall rule was the whole missing piece. you're the first working public seed this dapp has ever had. cheers i need sleep now
Whole thread · 10 replies →
H
@PriviMW found a repro for a dapp store bug in 1.8.1: Idios (1.3MB, CID Qma5bRLSsKReBZzdgERB6ArUZ18SFWJgsP4sqWKY15S91b) spins forever on install, fresh wallet, wifi and 4G, other dapps fine. the CID fetches in seconds from a plain go-ipfs node on the same swarm, and a user says it installed fine before the 1.8 update. happy to test a fix
P
Hi. How is dev work organized in beam? Do you have sync who implements what? What points from roadmap are addressed and where is lack of dev capacity? Do you have any calls or dedicated core dev channel?
Whole thread · 5 replies →
P
I`d be glad to know what are main 'streams' of ongoing work like backend, frontend etc, unless roadmap is top-level granulity

An open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog · Search · How we count