I’m interested even thought I’m not really sure what this is.
Discussion
Hello nostr:nprofile1qqsfev65tsmfgrv69mux65x4c7504wgrzrxgnrzrgj70cnyz9l68hjspr3mhxue69uhhyetvv9ujumn0wd68yctjv93xjcfwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszgrhwden5te0wfjkccte9e3xjarrda5kuerfwd68y6trwshx7un89uxwm93j
DamageBDD - https://damagebdd.com/ is a platform that lets anyone – not just programmers – describe how software should behave, using simple sentences. These sentences are written in a format called BDD (Behaviour Driven Development)
DamageBDD has systems which are currently being put in place to make everyone benefit from the product which covers people with technical skills and those with non technical skills
DamageBDD has a strong token on Coinstore which can be accessed and Traded through this link - https://coinstore.com/spot/DAMAGEUSDT
There's a lot to achieve from DamageBDD which I believe if you go through our social handles and telegram community you'll see a whole lot about the product and how to benefit from this great development
Ah common. Had to ruin it with a shitcoin.
bitcoin is money ... you think money can do testing infrastructure ... spare me the zealotry
It's like you saying Buying a Tesla Stock to get a Tesla model is a waste
DamageBDD has a token used to perform activities on its products so you can get results of your test or any other activity you intend to do on the platform
Close analogy to a standard token but $DAMAGE is not stock/token in the traditional sense .. it's a token which has one primary purpose to create an unbreakable chain of verification ... that's why the token exists and it has all the benefits of an first class Proof of work instrument of software verification ... so it's not token funds project ... token links verification
we tested zaps on this note… we made six attempts to⚡zap this note, at community@damagebdd.com, over a period of about 2 hours. six of the zaps were successfully paid... please check for 6 satoshis received. problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (the zap spec requires that the zap receipts be sent to the relays specified in the zap.) this means a nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... also fyi... your server at damagebdd.com is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 3440ms (3.4 seconds). we consider this slow... generally, zap invoices should be created in under one second. if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.