0x6837…56f6

All memos sent from and to 0x6837…56f6.

ipfs://QmSHkLhbPF96jYwYq52TmmvQNSCFijhZWYziRqgimBQ9Naattestations[com.x][atst.lighthousegov.eth]0xda6174737483021a69ea2b805841433396c929e0ccdccad97a340e23f1f9028e325ab1d1265f78a20eab7ac0ff55178e677bf5c98d4a5e1aad7b11c9165c0e52bb00b4ae38cfc536536b0dbb3c4f1buid[com.x][atst.lighthousegov.eth]0xda6174737483021a69ea2b805841559da70ac5be7c1552541cc9b768b87aa138e7f0b1d1ba9ccaede765544247df2c3213a4de8e83b28003430eedd66d6511478705ce09bce26cad39f6a2d184d01b
org.telegram.proof0xab6168677831613335653161706c6f72672e74656c656772616d61760263617474782a307837453546343535323039314136393132356435446643623762384332363539303239333935426466636578701a6a5685f663707266783e68747470733a2f2f73746167652e656e732e6f626a656b742e73682f3161333565312e6574682f626c6f622f6f72672e74656c656772616d2e70726f6f666373696758418b7d2a9ba8d6f63659b063a92034dd5617fc0520067f8be9686fddcb2b7783df27139082e3297991659746f6ebbd1bedbcd59985ae9e87bd45084bf35994dd7b1c63756964693335333435333333366461646472782a307836383337303437463436446131643564394137393834366232353831306239326164463435364636646e616d656a3161333565312e65746867636861696e496401
com.x.proof0xab616866316133356531617065636f6d2e7861760263617474782a307837453546343535323039314136393132356435446643623762384332363539303239333935426466636578701a6a56764563707266783768747470733a2f2f73746167652e656e732e6f626a656b742e73682f3161333565312e6574682f626c6f622f636f6d2e782e70726f6f66637369675841902d93d1918c0584195f53c8643eec88a01c95ff2dfc5a175965bd85e2982e4b2eb482db0edf3cd6482f39453ef68f17a6f1342be191e16f176608c8564a0a2c1c6375696473313335343733353532383935373132343630386461646472782a307836383337303437463436446131643564394137393834366232353831306239326164463435364636646e616d656a3161333565312e65746867636861696e496401
proof.twitter0xa961686631613335653161706774776974746572617601636578701a6a5657d863707266783968747470733a2f2f73746167652e656e732e6f626a656b742e73682f3161333565312e6574682f626c6f622f70726f6f662e74776974746572637369675841330ef1f61069b7c703f599491ddfe8b6bfb4775a6fb230c8eeb2d0663f9f2f69366fe8fd410864a0db4faa0550de7bb16bf850db17921fbfa531b7f289a452fe1c637569647331333534373335353238393537313234363038646e616d656a3161333565312e65746867636861696e496401
I think there is a disconnect vs what we are requesting in this proposal as part of the broader Lighthouse strategy. Appreciate your attempt at constructive feedback, but it has just reads different. In regards to Prop 540, it's a slightly different offering to the long term strategic vision of what we are attempting to do. To summarise, we are more just "proposal + comment notifications". I would highly recommend watching the demo we prepared which alludes to some of the longer term goals of what we are trying to achieve. https://www.loom.com/share/037327dbb0234df687fb991db805f8f6 The reason we do not detail them all in this proposal, is due to the general observation that the community is in favour of narrow goals and milestones over funding 12 month efforts with little accountability. Hope this makes sense, and appreciate your POV.
Hi lilfrog.eth, to say "I don't think lighthouse is currently promoting a feature set that is meaningfully different than any of the other clients we have right now." To be clear: * There is no native iOS/Android NOUNS client for proposals (to my knowledge) * Real time push notifications for Proposals + Comments does not exist elsewhere Thus a comment like the above is not very fair, to a client that is genuinely attempting and has achieved (with no grants to date) a feature set that significantly different to current clients.
better-nouns-support-in-lighthouseThanks for your thoughts lilfrog,eth. Will leave, jkm.eth to respond to the broader feedback. We have some thoughts on "feature requests" in general. As too many feature requests are lost in the comments, when they could be narrow scoped tasks. Hence our narrow scoped proposal. I would suggest NOUNs potentially adopt the OP Mission request format where NOUSs members can RFC for features, setting scope and budget and teams can submit their own proposals with respect to deadlines, milestones with amendments to scope if necessary. Which ideally should lead to a better outcomes, with regards to capital allocation, and holding implementers accountable. This should hopefully provide some background to our reasoning behind this proposal.
If I could add an addendum. New to this so apologies if this is already part of the process. I would avoid words such as “gifts” and and “thanks” at the end of the day if the goal is to proliferate FC, we should be working towards establishing some discrete vectors for measuring the “success” metric.
Lighthouse is a communications platform for web3 communities. We aim to enhance safety, accountability, and transparency for participants.\n\nWe are building guarantees around sender and message authenticity through cryptographic signatures, preventing imposters from sending messages to the community. It stores messages on IPFS or Arweave, creating on-chain records to ensure accountability for project leaders.\n\nFind us at ETH Lisbon and ETH CC.\n\nHolders of this token get:\n* Priority access to our private beta\n* Priority access to our native apps\n* Access to token gated dev channels\n* Early bird benefits (TBC)
LighthouseBEACONLighthouse is a communications platform for web3 communities. We aim to enhance safety, accountability, and transparency for participants.\n\nWe are building guarantees around sender and message authenticity through cryptographic signatures, preventing imposters from sending messages to the community. It stores messages on IPFS or Arweave, creating on-chain records to ensure accountability for project leaders.\n\nRecipients can be sure that messages received were sent by project leaders and not a malicious actor or compromised account.\n\nFind us at ETH Lisbon and ETH CC.ipfs://bafkreif5miql6sd3hdw3aoiwjxpioov4z4lwpaxiyivid4cp35zan3rrz4