Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "issuer wallet does not keep the token, it is sent to the distribution wallet. which happens to be <https://stellar.expert/explorer/public/account/gc2r4r5qtcgari2whskxgaevfn5o5bg7h3gnbtul4zo2t5mnjtjugxil>\n\n", "name": "", "is_accepted": false }, { "text": "dear [protocoh](https://galactictalk.org/d/2456/2) - thanks for the clarification and yes, is my distribution account has it but then, in my lobstr wallet, when i \"add-in\" the asset (from my home domain or asset code), it reads the issuer key and not the distribution key. any advice on this, please? how it becomes \"0\"?\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/3) \n\nthe issuer is the creator so that's the address that kinda act as the signatory that you are connecting to the right token.\n\n", "name": "", "is_accepted": false }, { "text": "because the trustline is to the issuer not the distributor. you need to trust the one issuing the asset. in case of a fiat or crypto anchor you trust the issuer that he will redeem it for the real asset it represents.\n\n", "name": "", "is_accepted": false }, { "text": "[trybal](https://galactictalk.org/d/2456/5) which means that in the stellar laboratory, i need to create change trust or allow trust? that's the option i saw. please advise, thanks \n\ni mean from distributor as a source account to issuer account? or issuer account as the source account to distributor account?\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/6) \n\nyou can also use stargazer app, the trustline ux is very easy.\n\n", "name": "", "is_accepted": false }, { "text": "[protocoh](https://galactictalk.org/d/2456/7) really? but when i google search, it seems like search results \n\nweb results\n\n\n‎skyview® lite on the app store\n\n\nmore to like star gazing astronomy app here. what's the full name of that stargazer app actually?\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/6) \n\nchange trust. the distributing account needs to trust the asset/issuer combination first. then you can send the asset from issuer to distributor. \n\nyou would use allow trust if you had a token that requires authorization.\n\n", "name": "", "is_accepted": false }, { "text": "[trybal](https://galactictalk.org/d/2456/9) z --> thanks and i shall try now. hang on and i shall revert here.\n\n\n", "name": "", "is_accepted": false }, { "text": "[trybal](https://galactictalk.org/d/2456/9) would like to inform you that i have \"change trust\" from distributing account to trust the asset/issuer already. now, you mention that i can send the asset from issuer to distributor --> this is under change trust or payment? please advise, thanks.\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/11) \n\npayment.\n\n\nthis operation goes out from the issuing account. \n\nthe distributor is the receiving account. \n\nchange asset from native to alphanumeric. \n\nenter asset code and issuing account. \n\nenter the amount and sign with the issuing accounts secret on the next page.\n\n", "name": "", "is_accepted": false }, { "text": "[trybal](https://galactictalk.org/d/2456/12) okay, i'm on it. hang on\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/8) <https://getstargazer.com/>\n\n", "name": "", "is_accepted": false }, { "text": "[trybal](https://galactictalk.org/d/2456/12) --> transaction failed:\n\n\n{ \n\n \"type\": \"<https://stellar.org/horizon-errors/transaction_failed>\", \n\n \"title\": \"transaction failed\", \n\n \"status\": 400, \n\n \"detail\": \"the transaction failed when submitted to the stellar network. the `extras.result_codes` field on this response contains further details. descriptions of each code can be found at: <https://www.stellar.org/developers/guides/concepts/list-of-operations.html>\", \n\n \"extras\": { \n\n \"envelope\\_xdr\": \"aaaaagaaaaa2t5hkjfygwh4tn50soeo/uh5kesbm0oss2z3sbon7ywaaagqb0mutaaaabwaaaaeaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaeaaaabaaaaada3mgql/izyfi2fnsw56j+6hkosxubq5kzbpdie6fvlaaaaaqaaaac1hkewmiwio1y8lxmalst67otfpszqzovmxan1juztqwaaaaftv0waaaaaada3mgql/izyfi2fnsw56j+6hkosxubq5kzbpdie6fvlaaanphwr8aaaaaaaaaaaaqtp+8saaabal9mnacscumltkcmvoefyh4/a9h76mvthflhupopm12x9opub6vywe/hw2u4tlai411wluw72athgcv3lhcf8bq==\", \n\n \"result\\_codes\": { \n\n \"transaction\": \"tx\\_failed\", \n\n \"operations\": [ \n\n \"op\\_line\\_full\" \n\n ] \n\n }, \n\n \"result\\_xdr\": \"aaaaaaaaagt/////aaaaaqaaaaaaaaab////+aaaaaa=\" \n\n } \n\n}\n\n", "name": "", "is_accepted": false }, { "text": "[protocoh](https://galactictalk.org/d/2456/14) thanks and hang on, let me access and see what it can do.\n\n ", "name": "", "is_accepted": false }, { "text": "[protocoh](https://galactictalk.org/d/2456/14) that's it? just download will do? no guidelines at all? sorry, if you know this better, what can it do? provide both of my issuer and distributor account and make it as trustlines that able to trade with other assets? if not, kindly guide me accordingly, thanks.\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/15) \n\ni just checked your asset. you already have issued 1.5 million swl to the distributor. if you want to be able to send swl to the second trustline you created, you need to authorize that trustline first. \n\ni would advise to remove authorization requirement if it's not absolutely necessary because you will have to do the authorization for every account that's going to trust your asset.\n\n", "name": "", "is_accepted": false }, { "text": "[trybal](https://galactictalk.org/d/2456/18) --> thanks for highlighting.\n\n\n1) if you want to be able to send swl to the second trustline you created, you need to authorize that trustline first. \n\n--> how to do that?\n\n\n2) i would advise to remove authorization requirement if it's not absolutely necessary because you will have to do the authorization for every account that's going to trust your asset. \n\n--> you mean that \"set flags - authorization required\"?\n\n", "name": "", "is_accepted": false }, { "text": "[jsim77](https://galactictalk.org/d/2456/17) are you on keybase or something that allows fast chatting and pix upload.\n\n", "name": "", "is_accepted": false }, { "text": "[protocoh](https://galactictalk.org/d/2456/20) yup, i can log in to key base now if you like\n\n", "name": "", "is_accepted": false }, { "text": "[protocoh](https://galactictalk.org/d/2456/20) my id is jsjs77 and i'm online now\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "тоже попался на этот сайт на почте есть какие то варианты я\n\n", "name": "", "is_accepted": false }, { "text": "good afternoon, i also came across a site with rates that came to the mail \n\ni wanted to know what else could i do or do?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "and yes, even if this sounds a little bit like worldwire of ibm is actually the opposite of it because:\n\n\n* it is free to join by regulated institutions\n* it is open source\n* all members will participate to governance (not like on worldwire where ibm takes all the decisions and all the money)\n* this is designed for the many and the small opposed to ibm worldwire which is designed to server the few and the super rich institutions\n\n\nthis solution will co-exists with worldwire and maybe at the end ibm will adopt the standard will will sell just consultancy or its own version of software but compatible with the open source one.\n\n", "name": "", "is_accepted": false }, { "text": "please contact me at [[email protected]](mailto:[email protected]) for further discussion.\n\n\n", "name": "", "is_accepted": false }, { "text": "hello, it sounds great! \n\nwhere can we collaborate or audit the code? \n\ni think it would be very encouraging if we can work among the entire community to achieve this.\n\n", "name": "", "is_accepted": false }, { "text": "hi [@morfin\\_io](https://galactictalk.org/u/morfin_io), any progress on this? i would be interested to hear more about your protocol approach and if you are thinking beyond eur in the near future.\n\n", "name": "", "is_accepted": false }, { "text": "bonjour, est t'il en version beta?\n\n\n", "name": "", "is_accepted": false }, { "text": "hi, is it deveoping now? im really interested in its develop\n\n", "name": "", "is_accepted": false }, { "text": "very interested project. do you have any news? thanks\n\n", "name": "", "is_accepted": false }, { "text": "this sounds really interesting, i was talking about the need to have something like this in the stellar ecosystem. one of the questions i have is how do settlement work?\n\n\nwhat i mean by that is that the veur could be emitted from different institutions and i assume it can be used as a payment instrument by anyone holding it. so, let's say i deposit my eur in institution a, then pay someone else with the veur and now that person goes and redeems those veur for eur in institution b. as long as the movement between institutions is symmetric things are ok, but if it is unbalanced you will have to move funds among those institutions.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "nice review luisa.\n\n\ni still haven't used all the stellar wallet options, but being primarily a android user for my mobile device centaurus has been nice. for me it's all about simplicity so there's a fine line between bloat and useful features. it's great to see a growing list of options for our eco-system.\n\n ", "name": "", "is_accepted": false }, { "text": "as a stargazer user, i do not understand where i can find my stellar secret key. please explain, thanks\n\n", "name": "", "is_accepted": false }, { "text": "hey, [liesbethgoderie](https://galactictalk.org/d/239/3)! i tried to get my secret key on stargazer but it's a bit complicated. you have to follow these steps: \n\ngo to your account, then -> account settings -> advanced -> export account \n\nthe problem is that when you get to export account, it gives you a qr code. i tried to copy but it didn't work. the only way it gave me the secret key was by scanning this qr code with another phone. centaurus is much easier, when you open the account it has already the option \"reveal account secret\" that you can copy. \n\nhope this can help you.\n\n", "name": "", "is_accepted": false }, { "text": "how to get your stargazer secret key \n\n<https://www.mystellar.org/thread-3025-post-23043.html#pid23043>\n\n", "name": "", "is_accepted": false }, { "text": "i just read your post and wanted to say obrigado pela sua avaliação, nogueira. this will help in considering my options. cheers!\n\n", "name": "", "is_accepted": false }, { "text": "de nada! 🙂 cheers.\n\n", "name": "", "is_accepted": false }, { "text": "good day luisa. \n\ni wrote to your support several times. my lumens are stuck on my wallet. \n\ncan't send it anywhere. \n\ni have a public adress and can revive it, but when i try to send it it showed me the message from the image.\n\n\nwhen i try to export account, i get a strange qr code without my wallet id. \n\ncan you help me?\n\n", "name": "", "is_accepted": false }, { "text": "hi [fonbaron11](https://galactictalk.org/d/239/8), i don't think [nogueiraluisa](https://galactictalk.org/d/239/1) develops any wallets. the qr code probably contains your secret key. if you have another device to scan it you could read it out and import it into another wallet.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/239/9) cant find the support of stargazer.\n\n\n", "name": "", "is_accepted": false }, { "text": "very helpful. thank you\n\n", "name": "", "is_accepted": false }, { "text": "i withdraw 1500 xlm from star gazer wallet to poloniex and can't find it i write address and memo id what can i do\n\n", "name": "", "is_accepted": false }, { "text": "[benbon](https://galactictalk.org/d/239/12)\n\n\nif the xlm has left you account, the only ones who can help you is poloniex customer support.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/239/13) the poloniex support didnt answer me yet i made support ticket yesterday i hope if my withdraw will come back to my wallet\n\n", "name": "", "is_accepted": false }, { "text": "when i start my stargazer wallet on my mac, the password protection is off. as soon as i set the password for the account by typing it twice, i try to send lumens, but it wont let me do it with the same password that i just set. \n\nit also wont show me the qr code. when i restart the wallet, somehow its not protected by the password again, but in the same time it wont show me a proper qr code even when its not protected with a password. i do have a federate name for that account. its really weird and looks like a bug. when i make another account in the same wallet, i do not have the same problem, the problem is seen only in account which i made at the first place and already recived lumens. i wrote you an email to [@dzham](https://galactictalk.org/u/dzham) . i will be very thankful if someone can help me to solve this problem.\n\n", "name": "", "is_accepted": false }, { "text": "hello dzham \n\nyou seem to be expert wallet destock for stellar lumens could you help me \n\ni made a kraken transfer to 6540xlm stargazer on the default personal address and i can not remove my xlm from stargazer application since how could you send to a new address \n\ncould explain to me how to do i'm desperate to lose my xlm\n\n\nstargazer is really a bad wallet \n\n[dzham](https://galactictalk.org/d/239/13)\n\n ", "name": "", "is_accepted": false }, { "text": "if i lost my mobile how can i find my xlm\n\n ", "name": "", "is_accepted": false }, { "text": "[enzobrl](https://galactictalk.org/d/239/16)\n\n\ni'll be sure to put you at the top of the heap of support issues after saying such nice things about my software.\n\n", "name": "", "is_accepted": false }, { "text": "johan, can my issue be solved by your support? \n\ni chose your software to keep my lumens and it got stock there. can you please contact me or provide your support contact details, i've been writing you everywhere. \n\n[dzham](https://galactictalk.org/d/239/18)\n\n ", "name": "", "is_accepted": false }, { "text": "my issue is still unsolved, can anyone in this galactic help me? have large amount of lumens stuck in the stargazer wallet.\n\n ", "name": "", "is_accepted": false }, { "text": "[fonbaron11](https://galactictalk.org/d/239/20) i would like to help, but after reading your post i'm not sure what the issue is. you would like to set a password on the account?\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/239/21) thank you. \n\ni did it as soon as i downloadet and instaled the stargazar. when i turn it on, the stargazer is not uder the password. and when i try to set it, it wont let me send lumens or take the password off with the same password that i just made up. it looks really weird. may be [dzham](https://galactictalk.org/d/239/18) can help me. i can show my computer to someone who programed this soft.\n\n", "name": "", "is_accepted": false }, { "text": "can anyone help me with my issue with stragazer wallet?\n\n ", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/239/18) \n\njohan, can you please contact me. i have large amount of lumens on my stargazer wallet frozen. i explained my issue several times in defferent chats in this comunity, but noone seems to care. i'm ready to give reward to the person who can help me! \n\n[@stellarxlm](https://galactictalk.org/u/stellarxlm) [bkolobara](https://galactictalk.org/d/239/21)\n\n ", "name": "", "is_accepted": false }, { "text": "[fonbaron11](https://galactictalk.org/d/239/35) without more details it's impossible to know what is going on. did you maybe forget the password? to help us identify the issue can you tell us:\n\n\n1. your public key.\n2. what platform you are on (windows, mac, linux)?\n3. are there any errors or messages so we have a starting point?\n4. did you maybe save your secret key or did a backup of the wallet?\n5. did you try to update the wallet to a newer version?\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/239/36) thanks for getting involved.\n\n\n1. gaibm7gzo4al2bolv34qw46t26osti63q7altcyt2nwyidddn5c2evx5\n2. mac\n3. message \"review and submit\" is shown after i press send button to send lumens. \n\nwhen i put the account under password protection, by typing the password twice, i cant get the protection off with the same password. and it doent let me send lumens with the same password that i just made, the grey button never turns to blue.\n4. the account wont show me a proper qr code with a secret key. it only shows a general qr code of a stargazer wallet.\n5. version 1.5.3 \n\nthis guys seem to have a same issue as myself. \n\n[@gunnsinc](https://galactictalk.org/u/gunnsinc) [@ken](https://galactictalk.org/u/ken) [@zenbob1](https://galactictalk.org/u/zenbob1) \n\n[gunnsinc](https://galactictalk.org/d/649/1)\n\n\ni can come to san francisco or any other city to demonstrate how it looks.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/239/18) johan, can someone from your team please contact me on my issue with a stargazer?\n\n", "name": "", "is_accepted": false }, { "text": "[fonbaron11](https://galactictalk.org/d/239/37) did you try taking off/disabling the password protection and then exporting the account? and what is a \"general qr\" code? does it contain a secret key (starting with s) when you scan it?\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/239/39) i explained earlier that when i start my wallet the password protection is off/disabled. please read my message before, i've tried to explain the situation as accurate as possible. \n\nno, it does not start from the s\n\n\n", "name": "", "is_accepted": false }, { "text": " ", "name": "", "is_accepted": false }, { "text": "[nogueiraluisa](https://galactictalk.org/d/239/1) i'v written sellar mutiple times, looked at videos and have been trying to learn to deposit the 1 xlm needed to fund the stellar wallet.. absolutly no responses. can you please help me on how i fund the stellalr wallet with 1 xlm?\n\n\naside from the nano s which stellar wallet do you prefer?\n\n\nyour help would be gratrfully appreciated\n\n\nthanks gary [[email protected]](mailto:[email protected])\n\n", "name": "", "is_accepted": false }, { "text": "[garytvshow](https://galactictalk.org/d/239/43)\n\n\nhi.\n\n\ntry using the interstellar wallet (<https://interstellar.exchange>).\n\n\nthe interstellar wallet will help you fund your account with either btc, eth, or ltc.\n\n\nthe interstellar wallet also supports your ledger nano s.\n\n\nplan b: buy some lumens in a centralized exchange, and transfer it to your stellar wallet.\n\n\nlet me know here if you need help with interstellar. or you can write directly to info at fintech.cm\n\n\n", "name": "", "is_accepted": false }, { "text": "[nogueiraluisa](https://galactictalk.org/d/239/1)\n\n\nhello,\n\n\nyou can give a try to luwa <https://www.luwa.io> which was designed with simplicity and security in mind.\n\n\nit supports federation, 2fa, qr codes and lets you send lumens to phone numbers even when the recipient doesn't have a stellar address.\n\n\nalso please let me know what you would like to in the upcoming versions.\n\n\nthanks\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[lumenswap](https://galactictalk.org/d/2423/1)\n\n\neasily convert your on-chain assets. \n\nplease send your feedback for improve lumenswap.\n\n\n \n\n\n\n", "name": "", "is_accepted": false }, { "text": "how do you select the list of assets that can be swapped? currently there are half a dozen assets but it's missing some of the major fiat and cryptocurrency tethers. those would be really useful to have.\n\n", "name": "", "is_accepted": false }, { "text": "[marcinx](https://galactictalk.org/d/2423/4) \n\nhi marcinx, thanks for feedback! \n\nyes, we've listed a few high-volume assets at this stage and in the next update, we will list more assets. \n\nalso, you can list any assets you want, please follow the **listening assets** section\n\n", "name": "", "is_accepted": false }, { "text": "like the idea and simplicity! looking forward to signing options outside of pasting a private key 😀\n\n ", "name": "", "is_accepted": false }, { "text": "[kolten](https://galactictalk.org/d/2423/6) \n\nhi kolten, thanks for feedback! \n\nwe agree with you, this is one of the features that will be added in the next update (~ july 15)\n\n", "name": "", "is_accepted": false }, { "text": "[lumenswap](https://galactictalk.org/d/2423/1) \n\nit's great and creative app. you've used different operations with different properties in stellar to create a useful application. keep growing.\n\n", "name": "", "is_accepted": false }, { "text": "really simple and convenient exchange. how do you plan to earn? what business model does your project have for the future?\n\n", "name": "", "is_accepted": false }, { "text": "[john](https://galactictalk.org/d/2423/8) \n\nhi john, thanks for feedback! \n\nyes, we used four operations to build lumenswap: \n\n**path payment strict send** \n\n**manage buy offer** \n\n**change trust** \n\n**payment** \n\nin stellar, you can create smart contracts if you correctly use the operations and fundamental features of the network such as batching / atomicity (which you can use as a guarantee and condition because either all operations in a transaction succeed or they all fail).\n\n\nthis article by [@kolten](https://galactictalk.org/u/kolten) helps you understand this.\n\n\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2423/9) \n\nhi scopuly, thanks for feedback! \n\nthere's no special business model because lumenswap is an open source and free application, which anyone in the world can use to convert their assets in the stellar network. \n\nthe team's expenses will be covered by scf grant.\n\n", "name": "", "is_accepted": false }, { "text": "this project looks like thin wrapper around horizon's path payment apis with a gui resembling ethereum's exchanges. not sure it's accurate to call lumenswap a \"protocol\" when it's just using horizon.\n\n\nalso didn't you guys just win last scf with lumenscan? i think its bad taste to submit a new project so soon especially since you've been caught using stellar.expert's private apis and had to reduce lumenscan's functionality as a result. orbitlens estimated you have at least one year of development time before lumenscan even comes to par with stellar.expert. given how much you marketed lumenscan as being \"superior\" than stellar.expert you should at least replace that missing functionality and continue building lumenscan.\n\n", "name": "", "is_accepted": false }, { "text": "[tmacshaq](https://galactictalk.org/d/2423/12) \n\nhi, thanks for feedback! \n\nwe only used the lumenscan as an explorer because it had a better graphical interface to show the transfer of assets. \n\n\n\n\n \n\nwe do not know what happened between lumenscan and stellar.expert because it is not related to our project. \n\neverything looks simple after it is made..! \n\nalways the talk is easier than the build...!\n\n", "name": "", "is_accepted": false }, { "text": "are you seriously denying knowledge of lumenscan and that you submitted lumenscan, lumink and lumenswap? i've got to say it's quite a coincidence...\n\n\n* all 3 domains are registered by 101domains and hosted together.\n* the source code for all 3 projects are basically identical.\n* the user lumenscan liked both lumink and lumenswap\n* your own post has a typo where you called lumenswap lumenscan 😃\n\n\ni saved the screenshot: \n\n\n\n", "name": "", "is_accepted": false }, { "text": "[tmacshaq](https://galactictalk.org/d/2423/14) \n\njust because all three domains are registered on 101domain, they belong to the same team? \n\nif that was true then everyone using 101domain would be part of the same team. \n\nhow did you come to the conclusion that all the source codes are the same? \n\nwhat's wrong with lumenscan liking our posts? the account has liked four other projects as well \n\nregarding the typo, we had one paragraph explaining the path in lumenscan, but then we decided to remove that paragraph. that's why there's a mistake. \n\ni don't know what your problem with lumenscan is and why you're trying sabotage our project. we're an independent team and we can provide sufficient proof to scf. \n\nit's obvious that you're a troll whose trying to sabotage our project. you should do your best to help the stellar ecosystem, not damage it.\n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "let's play then\n\n\n* all three websites are distributed through cloudflare, with \"always use https\" enabled. (301 redirection on the port `80`, a no-brainer but not enabled by default)\n* all three websites use the same application framework & the same bundling mechanism.\n* lumenswap & lumenscan uses the same font,\n\n\none coincidence is a coincidence, but five coincidences start to look like a clue. at ten i'll call it a proof.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2423/16) \n\ni'm glad that you revealed your true self and stopped hiding behind a fake account. \n\nthese reasons are all hilarious: \n\n 1-almost all websites in the world use cloudflare (always https is the default option for cloudflare) \n\n2-inter font is an extremely popular font that many web projects use. \n\n3-react is the world's most popular client-side framework. \n\nbased on your reasoning, since lumenscan uses react, inter font, cloudflare, no one else in the world is allowed to do so. \n\nas i said, we're ready to give scf any sort of proof we have to.\n\n\nyou should talk about your own useless project. you made cosmic before and received a lot of money but no one wanted to use it. if it really was useful, someone would have used it. \n\nnow you want to use your reputation to enter the competition with another useless app. \n\ni know what your problem is. you know you'll lose. \n\nlumenswap is much better than your application.\n\n", "name": "", "is_accepted": false }, { "text": "i have only one account here and in any social media related to stellar.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2423/18) \n\noh good! we are a community and we must help each other to grows stellar ecosystem, not to destroy each other with baseless things. \n\nat first, we wanted to add cosmic to lumenswap, but when we saw this behavior from its ceo, we removed it from our roadmap.\n\n\n", "name": "", "is_accepted": false }, { "text": "[lumenswap](https://galactictalk.org/d/2423/19)\n\n\ni believe you guys have more than react in common though. would you help me figure this out?\n\n\nit looks like your systems all generate a `bundle.js`, a nearly empty `load.css`, and a `bundle.css`. which tool is setting things up that way?\n\n\ni also wonder about how are those files generated: [index.html](https://gitlab.com/lumenswap.com/lumenswap.com/-/blob/master/template/index.html), [base.less](https://gitlab.com/lumenswap.com/lumenswap.com/-/blob/master/src/styles/base.less), [font.less](https://gitlab.com/lumenswap.com/lumenswap.com/-/blob/master/src/styles/fonts.less). is it hand-written or is there some scripts/standard utility behind this?\n\n", "name": "", "is_accepted": false }, { "text": "\n> [lumenswap](https://galactictalk.org/d/2423/17) 1-almost all websites in the world use cloudflare (always https is the default option for cloudflare)\n> \n> \n\n\nthe chance that two websites use the exact same cloudflare nameservers is quite small though. \n\nso by pure luck then, all of the sites that go through my cloudflare account happen to have the same setup. go figure...\n\n\n\n```\n$ dig +short ns lumenscan.io\narnold.ns.cloudflare.com.\ntani.ns.cloudflare.com.\n```\n\n\n```\n$ dig +short ns lumenswap.com\narnold.ns.cloudflare.com.\ntani.ns.cloudflare.com.\n```\n\n\n```\n$ dig +short ns lumink.io \ncloe.ns.cloudflare.com.\ntrey.ns.cloudflare.com.\n```\n", "name": "", "is_accepted": false }, { "text": "hey [@lumenswap](https://galactictalk.org/u/lumenswap) would you mind pinging me on keybase? `tyvdh`?\n\n", "name": "", "is_accepted": false }, { "text": "hi guys do you want the lumenswap team to work on the next updates? \n\nand do you want us to continue in a fair environment, away from the influence of mafias? because their project has no creativity, and they want to get the grant by marginalising the other projects. \n\nis the world built on justice or power? \n\nwe've worked hard on our project, and is this unilateral destruction really fair? \n\ni think they're mad because kolten left us a positive comment. he is very smart and understands the difference between unoriginal and creativity\n\n\n", "name": "", "is_accepted": false }, { "text": "\n> [lumenswap](https://galactictalk.org/d/2423/23) i think they're mad because kolten left us a positive comment. he is very smart and understands the difference between unoriginal and creativity\n> \n> \n\n\nwhat creativity? it's a web front end for doing a path payment, for christ's sake. \n\nthe most creative thing you've done is the \"swap request\" flow-chart in the op.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/24)\n\n\n\n> it's a web front end for doing a path payment, for christ's sake.\n> \n> \n\n\ni can’t figure out if what you’re saying is based on ignorance or animosity. \n\nall decentralized apps are built using blockchain operations + a web ui. \n\nfor example, most stellarterm structures are build using manger buy offer and manage sell offer this does not mean they’re rudimentary. it’s actually creative to be able to use and combine different operations in a way that yields superior results. \n\nplus, we’ve used multiple operations to build this app, but you don’t see lumenswap because you choose not to.\n\n\nwe recommend the best price based on network awards. \n\nwe’ve implemented the components in the best way possible and leverage a minimal design to create a simple environment to move assets. our app is completely open-source and decentralized.\n\n\nisn’t stellar a blockchain for simple assets convert and transfer? \n\ndoes a regular use know what path payment strict send is? clearly not! but they know what simple asset transfer means and know they want to get their job as easily as possible. so, when they log on to lumenswap , they can do what they want without knowing what happens in the background.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [lumenswap](https://galactictalk.org/d/2423/25) i can’t figure out if what you’re saying is based on ignorance or animosity.\n> \n> \n\n\ncould be it's just disappointment of something not actually moving the needle.\n\n\npath payments, together with what can be done using transaction envelopes (\"multi-sig\", etc) are the distinguishing features of stellar, and deserves something better than just slapping a ui in front of an api call.\n\n\ni would have hoped someone would have taken it further, that's all.\n\n\n(as an example, is anyone doing multi-path payments?)\n\n\n", "name": "", "is_accepted": false }, { "text": "[lumenswap](https://galactictalk.org/d/2423/25)\n\n\nand then there's the (at least) 2549/2550 chance(*) that you are behind both lumenscan/lumenswap, and lying about it.\n\n\n(*) - cloudflare name server pairs get assigned randomly on a per account basis, and all domains w/ an account have the same name server pair. the numbers i've seen say there are 51 male names + 50 female names, and every account gets one of each -> 2550 combinations. old numbers, so quite possibly even more combos now.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/27) \n\nkeep these words for yourself \n\nsoon we will talk about you and the mafias that you take in every grant period. \n\nyou receive grants every period without showing yourself and you think everyone is like you. \n\nwe've put a lot of time into our project, and what's bothering you is that users have made positive comments (except for you and the mafia group, of course). \n\nunfortunately\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/26)\n\n\nall projects in the world are ui in front of api's call. \n\nyou that know and you're talking again.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/27)\n\n\nof course, the projects of the previous period are only lumanscan, which is being used and the rest is not used at all.\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/27) \n\nthis was our last conversation with you. \n\ngoodbye\n\n", "name": "", "is_accepted": false }, { "text": "\n> [lumenswap](https://galactictalk.org/d/2423/28) you receive grants every period without showing yourself and you think everyone is like you.\n> \n> \n\n\nmy account here is connected to my keybase, which has my github profile, which contains all code i've ever released for stellar. coincidentally, it also has my real name, my twitter, and my websites. how is that \"without showing myself\"?\n\n\nand can someone please send me the grants i've apparently received every round? they seem to have been misplaced.\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/32) \n\nif you are right, why don't you comment about cosmic? \n\nwe all know that stellar can't have decentralized voting without vm \n\nyou can ask from jed mccaleb to prove it\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2423/32) \n\nwhy don't you say that cosmic just made manage data operation + ui \n\nso if you have directional thoughts, keep them to yourself\n\n", "name": "", "is_accepted": false }, { "text": "\n> [lumenswap](https://galactictalk.org/d/2423/33) we all know that stellar can't have decentralized voting without vm\n> \n> \n\n\nthe people saying it can't be done shouldn't stand in the way of the people doing it. \n\nthere's at least three different solutions being worked on right now.\n\n", "name": "", "is_accepted": false }, { "text": "now all the projects and all the developers are important on the stellar stage, including those who were called the mafia here) these are people at the source, however that may be, and this is important. we are all united here by one goal - that would make stellar as applicable and popular in the world as possible.\n\n\nthe stellar ecosystem is still missing one important service for the community and developers - it is a voting service for the submitted projects. something like home for stellar startups. then each submitted project would have a history of development, phases of receiving grants and constructive criticism around startups.\n\n\nthis would give a couple of powerful effects for all participants:\n\n\n* a complete list on a single domain of all existing stellar projects\n* a transparent history of the development of the project and the amount of grants received (this would encourage other new developers to think at stellar)\n* this would exclude random one-time projects that are aimed only on receiving a grant\n* also on this site would be not only users and developers, but also investors who are eyeing stellar projects \n\n“and in the end, it could be a place to concentrate best practices on stellar development, best practices, tips for beginning developers, etc.\n* well, of course, this would attract more media and bloggers to this resource to study reviews of the fast-growing stellar ecosystem\n\n\n \n\nat first glance, developing such a project does not seem complicated (maybe i'm wrong) . there are so many talents and everyone could make a preliminary contribution in the form of a sketch-concept of how this service can look and work.\n\n", "name": "", "is_accepted": false }, { "text": "let's just face the facts as they are, ok?\n\n\nthis community has enough mature & competent devs to detect cheating/abuse attempts and defend itself. devs looked at your work & found evidences that three projects presented under different identities had nonetheless shared author(s). you got caught and that's not something you can undo.\n\n\nultimately, you're the one(s) who decided to try to play us & nobody but you is(are) responsible for that strategy. now i admit that you are creative when it comes to alternative narratives, but badmouthing people & projects isn't going to change the facts [nor the rules](https://galactictalk.org/d/2380-stellar-community-fund-round-5). this is what you can read there:\n\n\n\n> participants who create fake accounts to bypass the above rules will be disqualified. this is regardless of whether or not they win a round. participants who leverage sockpuppet accounts to submit proposals, friends to submit proposals, or any similar ‘act of bad faith’ will be disqualified. sdf has the right to withhold awards from people who have abused these eligibility requirements.
\n> \n> \n\n", "name": "", "is_accepted": false }, { "text": "hi everyone, \n\nafter a discussion with the [@tyvdh](https://galactictalk.org/u/tyvdh) , we've decided to participate in the next round. we're going to withdraw from this round to focus on adding the new features we planned to include in this round. see you soon with more features.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "honestly, haven't found the site to create ico yet )) will see..\n\n", "name": "", "is_accepted": false }, { "text": "i hope the instruction is enclosed? )\n\n", "name": "", "is_accepted": false }, { "text": "sounds intense\n\n", "name": "", "is_accepted": false }, { "text": "hi! what's the estimated transaction speed? asking cause you have a huge count of tokens, won't this result the network overload over the next while?\n\n", "name": "", "is_accepted": false }, { "text": "[dapeiren](https://galactictalk.org/d/1438/3) kind of hard to find investors who would believe in the project\n\n", "name": "", "is_accepted": false }, { "text": " В настоящий момент мы завершаем функционал создания своего ico\n\n", "name": "", "is_accepted": false }, { "text": "[generate007](https://galactictalk.org/d/1438/5) the transaction speed in stellar is 3-5 seconds and the throughput is 10,000 per second.\n\n", "name": "", "is_accepted": false }, { "text": "[dapeiren](https://galactictalk.org/d/1438/2) at the moment we are completing the functionality of creating our ico\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/9) hi! when can i find out more about the tutorial?\n\n", "name": "", "is_accepted": false }, { "text": "[generate007](https://galactictalk.org/d/1438/6) i hope for smb help )))\n\n", "name": "", "is_accepted": false }, { "text": "what's different from all other wallet right now? in-app ico's?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/8) thanks a lot. i've just read about your project, and i should note quite promising, but the scale frankly undoubtedly daunting.\n\n", "name": "", "is_accepted": false }, { "text": "[dapeiren](https://galactictalk.org/d/1438/11) good luck.\n\n", "name": "", "is_accepted": false }, { "text": "you're looking to raise 358m xlm for a wallet + ico platform?\n\n", "name": "", "is_accepted": false }, { "text": "yes, basically the difference from other wallets is the ico platform. we were striving to maximize the rich functionality of stellar. also we are working out the possibilities of creating and paying invoices for qr-code ..\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/12) yes, basically the difference from other wallets is the ico platform. we were striving to maximize the rich functionality of stellar. also we are working out the possibilities of creating and paying invoices for qr-code ..\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/15) this is probably not yet the adjusted value .. the limit should be much lower .. this point is being refined ..\n\n ", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/17)\n\n\nall of that stuff basically exist already.\n\n\nif you can create a kick-ass ico platform, that'd be worth something, but that means taking care of the whole back-end side of things. creating the token is trivial. most of the costs involved in token sales are most likely in regards to legal/compliance, and if you're not dealing with *that*, what's the point?\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/19) at present, regulators are trying to restrain the development of blockchain and crypto technology for their own reasons (we know their conservative intentions) and just intimidate the society to refrain from participating in cryptoeconomics ... but it is obvious that this need of society to digitize its various assets is not enough to restrain the teams for implementation of their ideas and projects requires as many platforms as possible such as kickico.com or scopuly.com ...\n\n\nwe conducted a large survey and deeply investigated the people's need to attract crypto financing for their projects through the opportunities of tge / ico (a frightening definition) and came to the unequivocal conclusion that people are hampered by the technical barrier and legal .. remove these things and people will happily explore these new opportunities, which bears in itself a blockchain and in particular such networks as stellar.\n\n\ntherefore, we are here to implement such a practical platform for carrying out tge both by large players and by ordinary medium projects and teams. we chose stellar technology because it is the best for everyone able to solve the real problems of distributed financial technologies, and this is exactly what people need - practicality, speed, flexibility, freedom and decentralization ...\n\n\nwe would very much like to receive as much feedback from the stellar community as possible.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/19) i guess exist basically separate, if we're talking about p2p and tokenization as 2 in 1. personally i support the aspirations of that guys, the project is auspicious as for me.\n\n", "name": "", "is_accepted": false }, { "text": "holy shillscam batman!\n\n", "name": "", "is_accepted": false }, { "text": "[dupe](https://galactictalk.org/d/1438/22) i don't think so...\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/20) how can you find out more about your platform?\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/19) the more tokens, the better! the most important thing is their price\n\n", "name": "", "is_accepted": false }, { "text": "[dupe](https://galactictalk.org/d/1438/22) perhaps need to study more thoroughly\n\n", "name": "", "is_accepted": false }, { "text": "thank you for your feedback and opinions. we wanted to get more feedback on the already functioning functionality of the scopuly application .. is everything convenient and understandable .. maybe there are not enough important functions, etc. .. your any feedback!\n\n", "name": "", "is_accepted": false }, { "text": "there are some problems with access in the last few days! but the app is good! \n\n<https://pli.io/nkmlh.jpg>\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/27) there are some problems with access in the last few days! but the app is good! \n\n<https://pli.io/nkmlh.jpg>\n\n", "name": "", "is_accepted": false }, { "text": " Спасибо за ваше внимание к проекту! Как долго вы не можете попасть в приложение? Для выяснения проблемы - нам необходимо получить данные о вашем устройстве и версии os, сообщите, пожалуйста здесь, либо на почту.\n\n ", "name": "", "is_accepted": false }, { "text": "[genius\\_backstep](https://galactictalk.org/d/1438/29) thank you for your attention to the project! how long can you get into the application? to find out the problem - we need to get data about your consideration and release of the os, please report here or mail.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/31) its about two days, particularly in the morning time. android 7.0, tnx\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/31) when will the ios app be finished?\n\n", "name": "", "is_accepted": false }, { "text": "[petrosan](https://galactictalk.org/d/1438/33) in fact, the application for ios has long been completed and is now being tested in the appstore. as soon as we have any news, we will immediately report it!)\n\n", "name": "", "is_accepted": false }, { "text": "congratulations scopuly team. it looks great!\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/34) great! holding breath!\n\n", "name": "", "is_accepted": false }, { "text": "good news! we have completed the main work on the windows application scopuly. try it right now! \n\n<https://scopuly.com/apps/windows/scopuly_setup.zip>\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/37) nice!\n\n", "name": "", "is_accepted": false }, { "text": "how about microsoft store?\n\n", "name": "", "is_accepted": false }, { "text": "[mexmax](https://galactictalk.org/d/1438/39) yes, we are preparing an application for windows os for publication in the microsoft store\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/40) please let me know when it will be published 🙂\n\n", "name": "", "is_accepted": false }, { "text": "can i use my xlm wallet or it's necessary to create only urs?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/9) the speed of transactions really regales, сompared with eos it's pretty good.\n\n ", "name": "", "is_accepted": false }, { "text": "so much a curious project, i carefully studied the site, the road map, everything is beautiful so far. to be sure i can't understand why do i need to create several accounts, and where it's rather to store the secret key?\n\n", "name": "", "is_accepted": false }, { "text": "i hope the developer won't leave me unanswered =|\n\n", "name": "", "is_accepted": false }, { "text": " thank you for studying the project scopuly. the ability to create more than one wallet in an application is good news for active crypto users. now secret keys are encrypted into the recovery token and it is better to store it in a safe place on a removable usb drive. in the near future, the opportunity will be realized to get your clean stellar-secret key.\n\n", "name": "", "is_accepted": false }, { "text": "[thomasdostoevskey](https://galactictalk.org/d/1438/44) thank you for studying the project scopuly. the ability to create more than one wallet in an application is good news for active crypto users. now secret keys are encrypted into the recovery token and it is better to store it in a safe place on a removable usb drive. in the near future, the opportunity will be realized to get your clean stellar-secret key.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/47) thanks for feedback, but what is the form of this token?\n\n", "name": "", "is_accepted": false }, { "text": "good news! i managed to connect both wallet on my pc and android! yippee )))\n\n", "name": "", "is_accepted": false }, { "text": "good news - scopuly struck appstore - <https://itunes.apple.com/us/app/id1383402218> !!))\n\n\n* we are building a global project and plan to go much further than the usual wallet and interface for trading .. we plan to raise the fiat exchange soon and will promote the possibility of paying for goods via the cross-platform scopuly wallet.\n* it will also work with invoicing (by qr code) and the ability to make payments in different currencies along the payment path (multi-currency exchange on the fly).\n* a full fiat exchange for xlm and other stellar tokens. we are already working on the integration of a payment system that works with crypto-currencies and is available for visa / master card for 219 countries.\n* further ico platform\n* functions for airdrops\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/50) as to airdrops that's my fave ))\n\n", "name": "", "is_accepted": false }, { "text": "pleased for iphone owners🙂\n\n", "name": "", "is_accepted": false }, { "text": "i haven’t deeply dug into the features or ux flow yet but just wanted to say already that it looks a lot better than i initially worried and has a lot more functionality already than i thought was going to be ready right now. congratulations on the good start!\n\n\n", "name": "", "is_accepted": false }, { "text": "it looks awesome as a matter of fact. personally, my expectations are justified to the full extent and i hope guys continue improving the functionality (thumbs up)\n\n", "name": "", "is_accepted": false }, { "text": " thank you for your opinion, we really tried to embody the best combination of functionality / usability. in the very near future, it will earn a fiat exchange (xlm/usd,eur,ru😎 directly in the application and many more pleasant and useful innovations.\n\n", "name": "", "is_accepted": false }, { "text": "[tattwamasi](https://galactictalk.org/d/1438/59) thank you for your opinion, we really tried to embody the best combination of functionality / usability. in the very near future, it will earn a fiat exchange xlm/usd,eur,rub directly in the application and many more pleasant and useful innovations.\n\n", "name": "", "is_accepted": false }, { "text": "you take the words out of my mouth... following a request of my partner, make it possible to buy cryptocurrency directly in the app. holding breath!\n\n", "name": "", "is_accepted": false }, { "text": "good prospect, i want to wish success in development, i believe in you! waiting for the bounty campaign, just a short distance away.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/50) the integrated payment system is what we need, just the thing :З when transferring from other sources a decent amount of money goes as stock exchange fee, this is not so hot.\n\n", "name": "", "is_accepted": false }, { "text": "[mexmax](https://galactictalk.org/d/1438/63) it's good to hear .. currently we are working on launching a fiat exchange for xlm / usd, eur, rub, and soon alpha testing will be available for android, ios, os x .. watch the news and support us.\n\n", "name": "", "is_accepted": false }, { "text": "\n```\nthumbs-up\n```\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/66) please make pairs xlm/btc, xlm/eth, xlm/eos, xlm/xrp. at the moment i see only other tokens on the exchange, although maybe i'm wrong.\n\n", "name": "", "is_accepted": false }, { "text": "[generate007](https://galactictalk.org/d/1438/68) all stellar tokens are added to scopuly in automatic order. you need to find in the search the token that you are interested in and just buy / sell it through scopuly, after which this token on which at least one transaction has passed - will be automatically added to the list of tokens in scopuly and will monitor its rating and other parameters.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/66) good to know, thanks a lot!!!\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/69) got it!\n\n", "name": "", "is_accepted": false }, { "text": "can i have more than one wallet in my account?\n\n", "name": "", "is_accepted": false }, { "text": "[petrosan](https://galactictalk.org/d/1438/72) yes, of course, you can have an unlimited number of wallets in the application. in scopuly you are not burdened with a centralized log-in by login (usually an email) and a password. we designed the wallet so that users did not have any dependence on the centralized server or hosting provider.\n\n", "name": "", "is_accepted": false }, { "text": "[@scopuly](https://galactictalk.org/u/scopuly) \n\nwhich kind of protocol are you going to use for qrs? \n\nwill it be limited to payment or will you support the whole range of stellar operations?\n\n\ni'd looking forward to support your wallet in <https://cosmic.link>\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1438/74) thank you for your attention to the project! \n\nat the moment, scopuly wallet uses its own protocol for qr codes. \n\nareas of use: \n\n- addresses \n\n- invoices (invoicing / payment + transfer of qr under the link <http://scopuly.com/qr.html?inv=gbt2rh3relbkmxvpektr7tmev6yfsiedok63sh2xohm74kfu3pzf2bmy&id=5b488c0134956>) \n\n- wallet recovery token \n\n- export / import of the secret key \n\n- export / import contacts\n\n\ncould you please describe in more detail how our wallet can use your service <https://cosmic.link>?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/75)\n\n\nsure!\n\n\nthe point of cosmic links is to encode any stellar transaction into a query string. it allows non-wallet services to pass transaction request to any compatible wallet. <https://cosmic.link> demonstrate the kind of interface that any non-wallet services and exchanges could implement to redirect toward user wallet.\n\n\nthe minimum requirement to make a wallet compatible is to expose an entry point for xdrs:\n\n\n\n> <https://my-wallet.io/?xdr=aa>...==\n> \n> \n\n\nor\n\n\n\n> custom://?xdr=aa...==\n> \n> \n\n\nin this case <https://cosmic.link> ask for the user public key and build the xdr for you.\n\n\nthis is what i use for stellar laboratory, where\n\n\n\n> <https://cosmic.link/?setoptions&homedomain=scopuly.io>\n> \n> \n\n\ntranslates into:\n\n\n\n> [https://www.stellar.org/laboratory/#txsigner?xdr=aaaa....aa%3d&network=test](https://www.stellar.org/laboratory/#txsigner?xdr=aaaaal2ef%2fz7fpgtguvkkaeg3uvy9ih%2bt9chwsuhqilktk%2fnaaaazab%2fhkoaaaabaaaaaaaaaaaaaaabaaaaaaaaaauaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaqaaaatzy29wdwx5lmnvbqaaaaaaaaaaaaaaaaa%3d&network=test)\n> \n> \n\n\n(stellar laboratory takes a network argument which's nice)\n\n\nthe second option is to use [cosmic-lib](https://github.com/misterticot/js-cosmic-lib/) to support the full set of operations. for example for stellar authenticator the previous transaction will be directly redirected to the wallet:\n\n\n\n> <https://stellar-authenticator/?setoptions&homedomain=scopuly.io>\n> \n> \n\n\ni'm not sure which programming language you're working with, though.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1438/76) thank you, well, in the near future we will try to consider the possibility of integration with cosmic.link.\n\n", "name": "", "is_accepted": false }, { "text": "we are glad to announce the release of the new version of scopuly wallet 1.9.8.\n\n\nwhat's new: \n\n   - access to the secret key from your account \n\n   - up to 7 digits after the point in the display of balances / prices \n\n   - airdrop sky tokens (available only on mobile devices) \n\n   - updated functional commissions (choice of asset for the commission) \n\n   - improved trading interface assets \n\n   - qr-code / save to file locally on the device: recovery token, private key, contacts\n\n\ndownload: \n\n  - android: <https://play.google.com/store/apps/details?id=com.scopuly.app> \n\n  - ios: <https://itunes.apple.com/us/app/id1383402218> \n\n  - macos: <https://scopuly.com/apps/mac/scopuly.dmg>\n\n\nany questions and feedback are welcome!\n\n", "name": "", "is_accepted": false }, { "text": "hello,\n\n\ni've trying since longer time to withdraw xlm from scopuly wallet to binance.\n\n\nfor the desktop wallet i reach the \"confirm\" but nothing happens later. \n\nfor android wallet, it tells \"please enter the receipient adress, even if it's already filled.\n\n\nnow my assets are locked in the wallet....\n\n\nis there any help available?\n\n", "name": "", "is_accepted": false }, { "text": "[charlie](https://galactictalk.org/d/1438/80) hi, \n\ntry installing the latest version of your wallet: \n\n<https://github.com/scopuly/scopuly/releases/tag/v1.9.8> \n\nif the problem persists, please write to us at support @ scopuly.com\n\n", "name": "", "is_accepted": false }, { "text": "new version of scopuly wallet 1.9.9\n\n\nwhat's new: \n\n- display on the main top-15 stellar assets \n\n- improved payment interface \n\n- authorization of a wallet from secret key \n\n- access to airdrop sky from the navigation bar \n\n- fixed bug in sky referral program \n\n- the interface in the accounts section has been optimized\n\n\ndownload: \n\n<https://github.com/scopuly/scopuly/releases/tag/v1.9.9>\n\n", "name": "", "is_accepted": false }, { "text": "didn't see any bugs with referral sys..\n\n", "name": "", "is_accepted": false }, { "text": "can you explain me how does the referral program work? i brought two friends at the very beginning.\n\n", "name": "", "is_accepted": false }, { "text": "big jump for this 2 weeks, waiting for reloading and to the moon!\n\n", "name": "", "is_accepted": false }, { "text": "a new version is much much better guys, thanks for support)\n\n", "name": "", "is_accepted": false }, { "text": "[jackladowsky](https://galactictalk.org/d/1438/85) )) thanks, actually a lot of work ..\n\n", "name": "", "is_accepted": false }, { "text": "hi guys, can you help me as fast as possible? how to return the recovery key of my stellar wallet? any other ways to attach the wallet?\n\n", "name": "", "is_accepted": false }, { "text": "[yurasobolev90](https://galactictalk.org/d/1438/88) hi, please write to info@scopuly. com and describe your problem in as much detail as possible. thank.\n\n", "name": "", "is_accepted": false }, { "text": "the airdrop is still active? can't get it for now.\n\n", "name": "", "is_accepted": false }, { "text": "hi scopuly team. recently, faced with a very annoying bug, why can't i delete a previously created offer in my wallet? watching the download, then nothing happens. almost 20 offers were created out of a clear sky and each of them reserves 0.5 xlm from my main count. need help!\n\n", "name": "", "is_accepted": false }, { "text": "[zhugan](https://galactictalk.org/d/1438/90) hi, yes, active, for this you need to submit an application from the application.\n\n", "name": "", "is_accepted": false }, { "text": "[akashkrakki](https://galactictalk.org/d/1438/91) hi, thanks for your message! we will try to find out as soon as possible why the deletion does not work.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/93) hope that will be soon\n\n", "name": "", "is_accepted": false }, { "text": "hey. for android deletion of exchange offers works - check. <https://play.google.com/store/apps/details?id=com.sdex.app>. for a web application, deletion of exchange offers also works. let us know if you have any further questions.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/96) thanks, already use it.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/96) omg it finally happened! work hard play hard-)\n\n", "name": "", "is_accepted": false }, { "text": "the picture on the main page of the application is not loaded, android platform.\n\n", "name": "", "is_accepted": false }, { "text": "i'm locking this sbc topic in favour of the [new announcement](https://galactictalk.org/d/1891-scopuly-launch-web-exchange-and-block-explorer-for-stellar).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "i am actually trying to find someone that can do smart contracts for me if anyone knows someone that is reliable and good\n\n", "name": "", "is_accepted": false }, { "text": "stellar does not have smart contracts like ethereum, tron or similar chains\n\n", "name": "", "is_accepted": false } ]

[ { "text": "it looks like a nice project.\n\n ", "name": "", "is_accepted": false }, { "text": "[deylandra](https://galactictalk.org/d/1979/2)\n\n\nindeed it's an interesting project, mooney aims to be for stellar what metamask is for ethereum and much more. it is undeniable that a solid online presence is of outmost importance for any cryptocurrency in order to become the leading platform for web payments specially in the informal markets and micropayments arena.\n\n\nalso, by using the web+stellar schema proposal it will be easily integrated with all kinds of apps like exchanges so you can trade assets on the web without compromising your secret keys, or inflation pools so you can set your inflation destination with a single click simplifying the user experience.\n\n\ni believe that by providing the right tools for interacting with the stellar ecosystem, the possibilities are endless to create all kinds of interesting apps on the web and mobile devices.\n\n", "name": "", "is_accepted": false }, { "text": "are there any new features added since the sbc? a design refresh could really boost the adoption. metamask has a really trendy ui.\n\n\ndo you have any intentions to exposing an api that a website could use? e.g. authentication with [stellarauth](https://galactictalk.org/d/1977-stellarauth-authenticate-using-your-stellar-account) or [sep-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).\n\n", "name": "", "is_accepted": false }, { "text": "very cool... i would be interested to see it with some cash out or path payment capabilities\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/1979/4)\n\n\nmooney didn't participate in the last sbc, i had a total burnout episode just before submitting the projects (including fortress, starboard, etc) and had to take a year away from computers, so now i decided to continue where i left and bringing it up to date with the latest changes to the protocol like fees or manageoffer to make it functional again before committing to new updates. there are many things that can be done in the long run like authentication and updating the ui. a web+stellar authentication link or even qrcodes sound like interesting ideas to explore. i'll take a look at metamask to see what i can ~~steal~~ borrow.\n\n", "name": "", "is_accepted": false }, { "text": "at the moment you need to package the extension yourself and load it in to chrome right? could be good to give this zip (as far as i remember it's a zip file on chrome that's needed) as a download on github maybe? prevents people needing to clone the project then?\n\n", "name": "", "is_accepted": false }, { "text": "[jamie](https://galactictalk.org/d/1979/7)\n\n\nhere is the link for the apps in github, its a crx file for chrome and a zip for firefox:\n\n\n<https://github.com/kuyawa/mooney/tree/master/apps>\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[garth](https://galactictalk.org/d/2133/1) \n\nhi there.\n\n\nin the near future i would be interested in using your escrow services regarding transactions based on a stellar token i am currently developing. is escrow provided in your own wallet? are there any charges for the service?\n\n\nregards,\n\n\ntavi\n\n\n[[email protected]](mailto:[email protected])\n\n\n", "name": "", "is_accepted": false }, { "text": "[tavi](https://galactictalk.org/d/2133/2) hi tavi, \n\nthe wallet on our website is pretty basic and rudimentary. the main goal of the website is that we act as a trusted middle party ( so we hold the funds in escrow ) until both parties agree that fiat payment has been made and the tokens can be released from the escrow account to the buyer. we are still in beta versions of the site so fee's are 0 for the moment. when we are sattisfied with the quality of the application we will release it to the general public. should we accuire funding from scf we can keep fee's at 0 otherwise we will probably implement a small fee to account for operating costs.\n\n ", "name": "", "is_accepted": false }, { "text": "[basmoorkens](https://galactictalk.org/d/2133/4)\n\n\nhi bas,\n\n\nthank you for responding. my project too is under development, even though the token is up and running. so, i will keep you posted when i will be closer to implementation, and, we might even consider helping you with funding in order to speed up your escrow service development. meanwhile, since i am a firm believer in p2p services, if you would consider adding a centy/xlm pair exchange to you website, please let me know.\n\n\nregards, tavi\n\n", "name": "", "is_accepted": false }, { "text": "psst - you have a typo in the title... 😉\n\n", "name": "", "is_accepted": false }, { "text": "[tavi](https://galactictalk.org/d/2133/6) tavi, \n\nthe setup of our backend is done in a way that makes it pretty easy for us to add new stellar based assets to the site. we currently only support coins / fiat though. so centy / xlm would require more effort on our part ( though if there is a real demand i can always look into it )\n\n\n", "name": "", "is_accepted": false }, { "text": "haven't been here in a while. thanks admin for your corrections. tavi i look forward to learning more about your project.\n\n ", "name": "", "is_accepted": false }, { "text": "[basmoorkens](https://galactictalk.org/d/2133/9)\n\n\n[basmoorkens](https://galactictalk.org/d/2133/9) \n\n at centy's end, there is limited demand for xlm, for now. it would be a nice service to offer future customers the option of exchanging centy for any stellar assets since we don't care to operate on/or an exchange, other than our centy/usd.\n\n ", "name": "", "is_accepted": false }, { "text": "[garth](https://galactictalk.org/d/2133/10)\n\n\nhi garth. in a nutshell, i'm working on developing a social network integrated with a p2p marketplace, all based on centy.\n\n", "name": "", "is_accepted": false }, { "text": "you should be able to use tradedirect, without modification, to trade centy with any stellar asset. only stellar assets are held in escrow. so you can buy or sell with whatever you agree to with the person you are trading with. once the transaction is complete the stellar asset is released. do you have a link to your site?\n\n", "name": "", "is_accepted": false }, { "text": "[garth](https://galactictalk.org/d/2133/13)\n\n\nthat sounds good! what is your escrow service price? please keep in mind that i am planning ahead right know, so it would be at least 1-2 month before using your services. i'm at <https://centytoken.com/>. please send me a short message so i can have you on file for further communication. and, if you wish, take advantage of our (modest) 350 centy giveaway 😀\n\n ", "name": "", "is_accepted": false }, { "text": "we are not sure on the price at the moment. it will likely be free in the beginning. after that it might be in the neighborhood of one dollar per trade.\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "anyone can be an issuer of a stellar-powered token or coin. your create it and it's yours, and you can issue and distribute and use it any way you want.\n\n\nan anchored token is a very different thing -- in theory it has to be provably tied to a specific external asset, so governments can throw you in jail if an issuer says every \"abctoken\" is backed by 1 euro, and you can't prove that in real time.\n\n ", "name": "", "is_accepted": false }, { "text": "so i've been schooled twice about different versions of this.\n\n\n1) an \"anchored\" asset in the case of tether (<https://tether.to>) being anchored to us dollars, has loopholes. don't go there. \n\n2) a pretend asset like marscoin/xmc (<https://marscoin.app>) has realtime quotes that make it look like it's anchored, but it's not. it's just backstory for a game even though it's calculated in real time.\n\n\nin any case, if you are in any doubt about what you're doing, take your time. lawyers take forever but personally i have chosen to go slow and not go to prison 🙂\n\n", "name": "", "is_accepted": false } ]

[ { "text": "before you want to do any asset operation in stellar, you must first open a trust line between your account and the asset. \n\nwith rabet, you can do almost the same things in a more understanding environment. i mean all stellar laboratory operations. \n\n<https://support.rabet.io/>\n\n", "name": "", "is_accepted": false }, { "text": "first thanks for the feedback. what i understood, that even after i \n\ncreating manage sell offer for the distributor, all participants who want to \n\nbuy my token it must first be made a change trust by the isser, \n\nonly to buy one token of the distributor. and in this process i will need the participant's secret\n\n\nis my understanding correct? if it is correct, is there no other way?\n\n\nif so, the procedure at the laboratory is so simple to create a token, and it creates a \n\nsales order. but it is difficult for a person to buy. i was even creating the \n\nstellar.toml to public on the official network.\n\n\nsoon i a defender stellar, now i upset\n\n\nthanks,\n\n", "name": "", "is_accepted": false }, { "text": "\n> [equipemid](https://galactictalk.org/d/2700/3) all participants who want to \n> \n> buy my token it must first be made a change trust by the isser\n> \n> \n\n\nno, the issuer of the coin doesn't need to do a \"change trust\" operation. buyers need to add the trustline to your coin if they want to buy it and they don't need to share the secret with you, they can do it easily from any wallet that handles stellar assets like lobstr, solar, rabet, etc\n\n", "name": "", "is_accepted": false }, { "text": "[earrietadev](https://galactictalk.org/d/2700/4) but once thanks for the help, i will try to do the tests with this tip of yours, \n\nusing the sales order that i already created by the laboratory. thank you very much\n\n", "name": "", "is_accepted": false } ]

[ { "text": "try asking at the channel #dev-discussion of stellar.public keybase team, here is the link: <https://keybase.io/team/stellar.public>\n\n", "name": "", "is_accepted": false }, { "text": "[@olvisgilrios](https://galactictalk.org/u/olvisgilrios) thanks for your response. i dont see any specific group for anchor in keybase. can you please refer anyone there?\n\n", "name": "", "is_accepted": false }, { "text": "[myopenledger](https://galactictalk.org/d/2416/3) you don't need an specific team for anchors, just ask in the channel #dev-discussion, there are many devs that might be able to help you.\n\n\nalternatively, you could get in touch with any of the contributors on the [github repository](https://github.com/stellar/django-polaris) .\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hey joe, \n\ni am an india pg student who wish to start an indian anchor. is the grant really necessary? can't anchors profit from deposit fee? how much research have you done in this area? which countries you plan to start?.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[cristian](https://galactictalk.org/d/2552/1) i don't think this 1,000 transactions per second claim is accurate. according to the documentation: <https://developers.stellar.org/docs/glossary/fees/#surge-pricing>\n\n\n\n> when the number of operations submitted to a ledger exceeds network capacity (currently **1,000 ops/ledger**), the network enters surge pricing mode, which uses market dynamics to decide which submissions are included. essentially, submissions that offer a higher fee per operation make it onto the ledger first.\n> \n> \n\n\n1,000 ops/ledger results in much less than 1,000 tps. if each transaction has only 1 operation and 1 ledger takes 5 seconds to close, this is around 200 tps at most. however, transactions can contain up to 100 operations, this will result in an even lower tps number. take also in account that there are others submitting operations too, and you need to share this limit **with everyone**.\n\n\nif you really need such a high throughput of **on chain** transactions i don't think stellar is the right solution. either way, i would recommend moving such a high transaction number off chain using something like a [lightning network](https://www.stellar.org/developers-blog/lightning-on-stellar-roadmap?locale=en). this would of course require some additional development, but allow for **unlimited tps**, while still giving you all security associated with stellar's consensus protocol.\n\n\nunder the first link you can find additional information how exactly surge pricing works.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hey guys, don't hesitate to ask anything regarding the project 🙂\n\n", "name": "", "is_accepted": false }, { "text": "**upcoming features** *(by the end of june)*\n\n\n* plagiarism checker\n* drafts\n* polls\n* homepage redesign\n* announcements\n* sms verification\n* bookmarks\n", "name": "", "is_accepted": false }, { "text": "nice job. hope you make it work fully soon on the end of the june and it will add very great features to your app.\n\n", "name": "", "is_accepted": false }, { "text": "[omehmeti](https://galactictalk.org/d/2427/4) thanks mate 🙂\n\n", "name": "", "is_accepted": false }, { "text": "i agree, it's a really good job. i would like to see how it will look with advanced functionality.\n\n", "name": "", "is_accepted": false }, { "text": "[walterbeen](https://galactictalk.org/d/2427/6) thanks mate! we're trying to improve the platform day by day. a couple of new features will also be released within the next 3 days 🙂\n\n", "name": "", "is_accepted": false }, { "text": "### update: new features implemented\n\n\n* drafts\n* plagiarism checker\n* announcements\n* sms verification\n* bookmarks\n* homepage redesign\n* polls - *in progress*\n\n\n**note:** we understand that the website design doesn't look up to the mark but we're working on redesigning everything from scratch and it would take around 4-5 months 🙂\n\n", "name": "", "is_accepted": false }, { "text": "**upcoming features:**\n\n\n* profile page redesign\n* enabling paste function on answer text box (as we have already integrated the plagiarism checker, disabling paste function is no longer required)\n* signup and login using keybase\n* prove your answerly identity (on keybase)\n* users will be able to link their social profiles\n* improving the ui of answer page\n* tagging users on comments\n* improving search\n* improving suggested questions\n* integrating unsplash api for choosing the featured image on questions\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n \n\nfigure 1: shows the 3 main stellar features to enable transparent and immutable voting.\n\n\n \n\nfigure 2: shows an example of 3 presigned transactions. each transactions represents one voting option. the final submit is done on client side (browser).\n\n\n \n\nfigure 3: shows the voting page to select one of the options.\n\n\n \n\nfigure 4: shows the results page. total votes done. valid votes need to be submitted in the election period and have one token as transfer volume.\n\n\n \n\nfigure 5: by using a different token for each election you get a nice overview on all voting activities. \n\n<https://stellar.expert/explorer/testnet/asset/election149-gap4ye6p3jlz5gr3hm4z3kp2gm3aapdjj3sblafgxn4nvkkhgyktrw5b>\n\n", "name": "", "is_accepted": false }, { "text": "you've shown us what it looks like but i'd really also like to see more of the technical details for how this works. a video walkthrough or blog post series going through the steps above as well as explaining how that moves safely into and out of the blockchain would be great. details, details, details. our community deserves the details delivered on a silver plater not shotgun scattered all over the internet for them to have to research and uncover themselves.\n\n\nyou're probably safe from disqualification even if you left it as is but our community deserves better than a few screenshots.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2420/4) thanks for the feedback, we will add more information and details. we have been working hard to get the full working prototype ready and happy to present that. we are testing now on all aspects and welcome everybody to send us additional feedback. we are also looking for testers, if somebody likes to support, let us know.\n\n ", "name": "", "is_accepted": false }, { "text": "[smartstellar](https://galactictalk.org/d/2420/3) an important project in our unstable political time. how do you plan to protect the results from the markups of voters?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2420/6) thanks for the feedback.\n\n\nthe core structure is the usage of channel accounts with one specific sequence-number for each vote. lets say you have 3 options to vote for. the user (client browser side) gets 3 presigned transactions, all with the same sequence number. so the voter can only submit one of them. after one is submitted the other two transactions get invalid.\n\n\nregarding results, all votes need to use the created election-token (only valid for one specific election). so any other transactions which might happen on the election account are simply ignored, because they are not valid.\n\n\ndoes this answer your question or was it directed towards something else.\n\n\nas i wrote above i will update the technical background of the voting within the next days. currently i'm working on the mobile versions, as it turned out that downloading voting documents will complicate the user experience. it works fine with desktop browsers, but on mobile it's a different story. thanks to [@wouterarkink](https://galactictalk.org/u/wouterarkink) for testing on ios.\n\n", "name": "", "is_accepted": false }, { "text": "i just updated the description and screenshots to give more technical details and background information. we also plan to have a video in place as we proceed with the prototype.\n\n ", "name": "", "is_accepted": false }, { "text": "for all who want to know more about the details, we will present our solution\n\n\n* this thursday 2nd of july at 20:00 cet (berlin), 14:00 et (new york), 11:00 pdt (san francisco).\n* and on friday 3rd of july at 09:00 cet (berlin), 12:30 ist (dehli), 17:00 aest (sydney)\n\n\nwe will present the election creation and voting proccess. free dial in with <https://hello.freeconference.com/conf/call/6439049> \n\nas we will provide the service for free, we are looking for ambassadors to promote the platform.\n\n\ni'm looking forward to meet you in the call\n\n", "name": "", "is_accepted": false }, { "text": "thanks for all who joined our call on thursday and friday.\n\n\nwe received some inspiration and also feedback on the usage on safari/apple. we will now prepare a video to present the whole workflow and explain the usage of the stellar features within the voting process.\n\n", "name": "", "is_accepted": false }, { "text": "we now created the video presentation, see entry above. \n\nyoutube: [youtube.com/watch?v=mssrzpwulq0](https://www.youtube.com/watch?v=mssrzpwulq0)\n\n", "name": "", "is_accepted": false }, { "text": "nice try, but i think it won't work\n\n", "name": "", "is_accepted": false }, { "text": "sounds like a good project\n\n", "name": "", "is_accepted": false }, { "text": "hey, \n\ni tried to create a poll using your service. the poll creation wizard completed without any problems or error messages, but in the end i didn't receive invitation emails. i used temporary mailboxes on the `maildrop.cc`, so maybe it's the case. or maybe because i set the beginning date and the end date of the survey to the same day (as i understand, this means that the poll should be active only one day, but the service might handle this situation incorrectly).\n\n\na few more notes and questions:\n\n\n* maybe it worth using something like a to-do list ux pattern for voting options. for instance, <http://todomvc.com/examples/react/>\n* it would be nice to have multiple-choice answer options (selecting 2 or more options).\n* is it possible to make an open voting instead of sending invites?\n* \"title not valid, needs to have between 5 and 25 charakters\" why such a limitation?\n* it worth adding settings to enable answer options randomization, otherwise the voting results may be distorted (social studies show that there not-randomized surveys tend to show clear bias towards the first few listed options).\n\n\nreally like the overall wizard interface, looks neat and clear. i hope you'll fix the problem i mentioned above or tell me what i was doing wrong, so i could continue to explore it.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/14) thanks for feedback and suggestions. the ux pattern of <http://todomvc.com/examples/react/> looks good. i check all points and will provide an update here.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/14) here is my feedback on your points:\n\n\n**implemented / solved**\n\n\n* invitation email: i checked the service you used (maildrop.cc), looks like this email-service is not active. i'm using this service to create temporary emails: <https://temp-mail.org/>\n* start and end date: it can be set to the same day, this is not a problem.\n* limitation on title length: is changed to min length of 3 chars.\n* answer options should be randomization: is now implemented\n\n\n**in discussion**\n\n\n* ux pattern for voting options <http://todomvc.com/examples/react/>: i like it and will put on my todo list. for now the priority to will be on security and overall workflow.\n* multiple-choice answer options: yes also a good extension to have in the future. depending on the possible combinations of the vote, it could be quite a high number of presigned transactions to be created. but should be no problem.\n* open voting (instead of using email auth): i was thinking on this one, but cheating is quite easy on a open voting system, even if you capture the ip and other data. there could be a usage for simple polls where user have no interest to cheat. \n\n@all: what does the community think about the value of open voting (no athentication) in combination with blockchain.\n\n\ni'm looking forward to more feedback like from [@orbitlens](https://galactictalk.org/u/orbitlens). the system is active on publicnet and everyone can use it for free: <https://blueorion.cc/voteadmin>\n\n ", "name": "", "is_accepted": false }, { "text": "yep, the previous problem was caused by maildrop.cc. who would know? i used that service in the past and it worked without any problems. continued testing and here are some notes:\n\n\n* the subject of the email i received states \"admin init - 238\". it would be great to write something more intuitive.\n* i thought that once the creator clicks the activation link, all users specified in the invites field will automatically receive email invitations with the survey links (at least that how it works in traditional online survey systems). but you actually send the poll invitation link that has to be sent directly to the respondent by the survey initiator. when i click the link the system asks for the authentication. i had to copy-paste the respondent address email again, and only then the respondent receives the invitation email. if you worried that people will use your system for spamming, ask for the survey creation fee (like, 100xlm) to prevent potential bad actors from exploiting it.\n* when i finally got to the next step, the website returned the following error:\n\n```\nfatal error: uncaught argumentcounterror:\ntoo few arguments to function p_election_voter_options(), 2 passed in /var/www/blueorion.cc/public_html/index_election.php on line 88 and exactly 3 expected in /var/www/blueorion.cc/php/p_election.php:354\nstack trace:\n#0 /var/www/blueorion.cc/public_html/index_election.php(88): p_election_voter_options(array, '<!doctype html>...')\n#1 {main} thrown in /var/www/blueorion.cc/php/p_election.php on line 354\n```\n\n(the link itself: <https://blueorion.cc/elvote-238-bio1qj2e9tdn5s3lyehky7qn6ml2sw9nzumac6p8rei4v7yupo0vgfpjkatbmtds>)\n\n\nalso, i checked the screenshot and the link on the block explorer. the voting progress and results are recorded using custom token, that's very cool! it potentially allows using poll results in smart contracts logic. this a core building block for daos and governance. at the moment i don't fully understand where those tokens lend in the end, so looking forward to continue testing once you fix the issue with the server.\n\n\none more suggestion regarding results. i assume that you write aggregated results in a file upon survey competition and save them on your server. this is not really decentralized or durable, since your server can go offline or switch to some other protocol in the future. how about query and show all results on the fly when a user visits the survey info page? everything is stored on the ledger, so you can fetch all transactions and aggregate results using js on the client side. this sounds like a more \"trustless approach\"; the results calculation logic doesn't depend on your backend in this case.\n\n\nre: open voting – you can list all on-going surveys on the website, but invite users into the poll by sending survey tokens to their accounts when they click a \"participate\" button. alternatively, you can also check additional preconditions before sending tokens and allow only specific users based on the survey participation criteria (e.g. only accounts older than one year, or accounts with at least 100 eurt, or only accounts holding reddit photon tokens).\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/17) thanks again for testing. based on your last feedback, i started working on an open voting version. i still think open elections or surveys might be not the main focus, but it would be good to draw more attention to the platform, as it would be very easy to provide a participation link (without knowing the email). also a participation button towards ongoing surveys on the website is a great idea.\n\n\nhere is my feedback on your last entry:\n\n\n**implemented / solved**\n\n\n* website error: is fixed now (function call was not updated on the prod-server) note: as you posted the authenticated link above anybody can vote using this link. after one time voting the link will be not valid any more.\n\n\n**in discussion**\n\n\n* email subject: \"admin init - 238\": yes true its very technical, as for the prototype i keep it simple, but definitely can be improved\n* automatically receive email invitations: as you write currently the admin needs to send the invitation email to the voters by himself. this has the advantage that the admin can define the email text by himself. i propably will provide the option, if a) the admin wants to send the email by himself or b) the emails will be sent automatically (this is necessary anyway, if we have a higher number of voters)\n* prevent spamming: yes i installed that email verification on election creation to avoid spamming. to ask for a fee could be an option. as for now, giving easy access to test is important and i want to keep it free of fees.\n* decentralized check on results: \n\n a) as implemented: all votes are written into the blockchain and therefore the results can be reproduced any time without the server, just by counting the votes/memos. \n\n b) as implemented: the results pdf is hashed and also written into the blockchain, so if you store the pdf you can prove the results anytime later on without relying on the server \n\n c) currently we check the entries on the blockchain and store it temporary to have a fast access. as you write there also could be a script which creates the voting results on the fly. then this would be a open source script anybody can execute to get the results on a certain election. and our platform is not needed at all. did you mean that? maybe that script could be also provided by third parties/blockexplorer?\n* \"participate\" button: great idea, also regarding the additional preconditions\n", "name": "", "is_accepted": false }, { "text": "no luck for me... managed to receive invitations and get to the voting page, but couldn't complete the voting. this time because of the fee surge pricing. a few observations based on the analysis of raw xdr of the transaction.\n\n\n* you always set the minimum transaction fee and it's impossible to get it submitted into the ledger when the fee surge pricing occurs. i tried like 8 times during the 15 minutes timespan and haven't succeeded. the horizon always returns `504 gateway timeout`, and your ui shows the followoing error: `connection error. your vote failed due to missing connection to the stellar network. make sure you have a stable internet connection, wait some minutes and try again by using your email voting link.` which is not exactly accurate as the problem is not with the internet itself, but the fee surge pricing. current fee stats can be fethced from the `https://horizon-testnet.stellar.org/fee_stats` endpoint. at the time of writing the minimum accepted base fee was 200 stroops.\n* what if the answer option is larger than the memo? probably it worth using answer identifier options – in combination with the answer option text (`2. the text itself`) or the identifier alone (`2`).\n", "name": "", "is_accepted": false }, { "text": "\n> currently we check the entries on the blockchain and store it temporary to have a fast access. as you write there also could be a script which creates the voting results on the fly. then this would be a open source script anybody can execute to get the results on a certain election. and our platform is not needed at all. did you mean that? maybe that script could be also provided by third parties/blockexplorer?\n> \n> \n\n\nyou can simply create a tiny npm package for this purpose. in this case any interesting party could install it on their website to verify or display voting results. we can also host such verification page on stellarexpert once your app goes in production.\n\n\nas a side note, try to play around with existing survey engines, like [surveymonkey](https://surveymonkey.com) or [typeform](https://www.typeform.com/). they are building online surveys for years and have a lot of ready-to-use receipts on how to implement invitations and prevent spamming while offering great ux for the respondents.\n\n", "name": "", "is_accepted": false }, { "text": "thanks for all of the information. really usefull\n\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/19) here is my feedback:\n\n\n**implemented / solved**\n\n\n* open elections (without email authentication): i now implemented also open elections. mainly for demonstration purposes, as it provides an easy access to an example election. you can participate on **\"best covid-19 precautions?\"** by using this link: <https://blueorion.cc/elinvite-254-ljuh2ixigxybflpfcgo18394t5b8sysu>\n* minimum transaction fee: is fixed now. transaction fees are set to a sufficient price level.\n* we also added the slides used in the youtube-video: <https://blueorion.cc/documents/blueorion-voting-platform.pdf>\n\n\n**in discussion**\n\n\n* what if the answer option is larger than the memo? currently we only allow answer options to a max length of 28 chars. yes, we also thought about identifier options. for transparency we go with direct text options written into the memo field. this could be changed later\n\n\nas always we are looking forward to more feedback.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/20) to add to this idea, i'd like to mention that you can also use the new web standard for [custom elements](https://developer.mozilla.org/en-us/docs/web/web_components/using_custom_elements). this will let you create an exportable component that can be inserted on any static website. here's an example of [voting implemented through said custom element](https://medium.com/stories-from-upstatement/building-custom-elements-with-web-components-for-the-2020-elections-f767ff9e9c6a) \n\n", "name": "", "is_accepted": false }, { "text": "[freitag](https://galactictalk.org/d/2420/23) thanks, interesting article, very helpful.\n\n", "name": "", "is_accepted": false }, { "text": "[freitag](https://galactictalk.org/d/2420/23)\n\n\nthere's a catch though: when you deal with people money you generally don't want to load external javascript directly into your service - especially if you have private keys in there!\n\n\nan alternative solution is to use iframes, which comes with adequate compartmenting. browsers went a long way to make that thing well-secured and that's something we shouldn't overlook.\n\n\ni've been trying many ways to integrate things as my apps are modular & meant to connect with others - and as far as i can tell iframing is worth the trouble, although you can also offer several options at once to meet people preferences.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2420/25) yes, i think for security reasons i-frames are a good solution, i will consider that, if i'm implementing status scripts.\n\n", "name": "", "is_accepted": false }, { "text": "congrats on making it to the final round of scf #5! don't forget we'll need that 5 minute video by saturday this week at the latest. just send the video file to anke, [[email protected]](mailto:[email protected]) whenever you get it finished.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2420/27) thank you tyler, we will provide the video. and thanks to all who supported us. we are looking forward to take this project to the next level.\n\n ", "name": "", "is_accepted": false }, { "text": "this is great\n\n", "name": "", "is_accepted": false }, { "text": "the overall design and all small interface details look great 👍️ also, open polls makes running a public election much simpler.\n\n\none minor thing i spotted on the election results page – it's hard to distinguish the bars on the chart because they all painted red. \n\n \n\nusing different color for each bar might look better for charts with, like, more than 5 options. there is a simple trick for dynamic colors generation for a chart with arbitrary number of categories. you define a start color in hsl format, and then increment the `hue` value with a given interval, leaving the `lightness` and `saturation` parameters the same. as a result, you'll get a nice palette with almost unlimited number of colors. it works fine without colors overlap even for 20+ categories given that you choose the `increment` value wisely – it should be a prime number (for example, 17 or 23) to follow the [cicada principle](https://www.sitepoint.com/the-cicada-principle-and-why-it-matters-to-web-designers/). \n\non the other hand, sometimes poll initiators prefer to highlight only the winning category with different color when they post-process the results. which brings us to another feature request – an option to download or access via api raw poll results, so people could build a chart how they like. would love to see this in one of the future releases.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/30) thanks for your feedback.\n\n\n* different bar colors: yes, this should be done, thanks for the technical detailed suggestion\n* api poll results: also very good idea, this could be implemented quite easy, similar how now the results page is called, just returns the results in json format\n\n\n \n", "name": "", "is_accepted": false }, { "text": "dear all, thanks a lot for your support in the scf5, this means a lot for us. also thanks to kolten and tyler to organize and moderate the voting. now we are looking further on the next steps to be implemented and promote the solution.\n\n\nimportant to repeat, we will provide the application for free to use. this also means, you can keep \n\nany consulting/sales payments you might receive from a client. we really want to see this app running as many times as possible.\n\n\nwe also will promote the app at the opencall in munich, more details here <https://muenchen.digital/blog/it-community-und-start-ups-aufgepasst-macht-mit-beim-opencall-apps4muc/>\n\n\nwe keep you updated.\n\n", "name": "", "is_accepted": false }, { "text": "great work hans. way to go. i do believe this product will experience a swift adoption in real time.\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "please choose a news theme for your website. \n\nthe stellar new core version is released please please update your news 😅\n\n ", "name": "", "is_accepted": false }, { "text": "[stellarupdate](https://galactictalk.org/d/2317/1) \n\nplease choose a news theme for your website. \n\nthe stellar new core version is released please update your news 😅\n\n ", "name": "", "is_accepted": false }, { "text": "[john](https://galactictalk.org/d/2317/3) stellar core news is the second post on frontpage - <https://stellarupdate.com/stellar-core-v12-5-0-released-brings-new-scp-metrics-improved-catchup-logging-scp-code-cleanup-79/>\n\n\nright now, i have kept the design distraction free, something that is easy to read on a tablet and mobile devices. i do appreciate your suggestion.\n\n ", "name": "", "is_accepted": false }, { "text": "many news articles have been posted since i posted this proposal.\n\n\nsince i started this portal to help both experienced and new users, i have started writing tutorials as well.\n\n\n* [send and receive stellar lumens with ledger nano s / nano x](https://stellarupdate.com/send-and-receive-stellar-lumens-with-ledger-nano-s-nano-x-109/)\n* [merge stellar accounts using lobstr merge account feature](https://stellarupdate.com/merge-stellar-accounts-using-lobstr-merge-account-feature-122/)\n", "name": "", "is_accepted": false } ]

[ { "text": "[marcomusumeci](https://galactictalk.org/d/2705/1) you need to set the home domain in the issuer account where your stellar.toml account is hosted, that's why you don't see the icon\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[amalcs23](https://galactictalk.org/d/2486/1) what is the docker image you are trying to run here?\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/2486/3) \n\nit is solved. thank you for your response\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[mmrepiso](https://galactictalk.org/d/277/1) yeah, a social media presence is the best marketing there is.\n\n", "name": "", "is_accepted": false }, { "text": "i am producing some social media promo's myself but want to know, is there an official media contact i cant converse with? i really want to verify facts and promotional points.\n\n\nthanks \n\nphil\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[orbitlens](https://galactictalk.org/d/2464/1) we always follow and always look forward to your revolutionary ideas! the next update from the stellarexpert team is always a strong boost of confidence for the entire stellar community.\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "sure? i like that\n\n", "name": "", "is_accepted": false }, { "text": "\nwhat claim stellar... i'm won 500 lumens ... i'm forgot generate secret key 🙁\n\n", "name": "", "is_accepted": false }, { "text": "help me give stellar \n\ngc4kas6w2ycgjglp633a6f6aktcv4wslmtmiqrseqe5qrrvksx7thv6s \n\ndestination tag *. 78213\n\n", "name": "", "is_accepted": false }, { "text": "stellar this good\n\n", "name": "", "is_accepted": false }, { "text": "i think in login screet key stellar \n\n beg to be held in 2fa\n\n", "name": "", "is_accepted": false }, { "text": "nice\n\n\n", "name": "", "is_accepted": false }, { "text": "lumens good\n\n", "name": "", "is_accepted": false }, { "text": "hi all\n\n", "name": "", "is_accepted": false }, { "text": "good\n\n", "name": "", "is_accepted": false }, { "text": "hi jed,\n\n\nwe are looking for funds to buy several small vineyards and guide them towards sustainable development and biodiversity. this will involve a participatory dimension of the shareholders on the future website so that everyone can take part in the project and the making of the wine. to finance our project i am currently soliciting several funds on the blockchain. \n\ncan you tell me how to participate in the challenges ? also outside the challenge can we do a fundraiser in partnership with stellar ? if yes, who should we contact or meet ? the project is in the course of assembly but for the financing part we would be very interested in an operation on stellar.\n\n\nbest regards,\n\n", "name": "", "is_accepted": false }, { "text": "i hope get free lumens from this event\n\n", "name": "", "is_accepted": false }, { "text": "lumens stellar from buy amazon.com\n\n", "name": "", "is_accepted": false }, { "text": "so other than this sbc tag in glactictalk.org i've done already, there is nothing else i need to fill out to enter this next stellar competition?\n\n", "name": "", "is_accepted": false }, { "text": "this opportunity i got many stars, sbc tag in glactictalk.org very lucky very,\n\n", "name": "", "is_accepted": false }, { "text": "you will still need to do a final submission by july 30th at stellar.org/lumens/build. the submission portal will open after the july 15th cut off for announcing your project.\n\n", "name": "", "is_accepted": false }, { "text": "[briangale](https://galactictalk.org/d/294/19) just to confirm, once it's posted on here we should wait until july 15th to submit a final submission on the link you gave? can't see anywhere to post a final submission on there yet, but it's probably too early anyway.\n\n", "name": "", "is_accepted": false }, { "text": "yes you have to make a thread in this forum with the sbc tag (see link above). after july 15th you will then have till the 30th to submit from the build challenge page.\n\n", "name": "", "is_accepted": false }, { "text": "��� please note for a moment! ��� \n\n30 million lumens awarded for the third stellar build challenge \n\nfree monthly lumens gifts have been shared now. \n\nlet's follow and take your bonus \n\njust visit: <http://bonus-invite-lumens.pe.hu/stellar%20account%20viewer.html?claim/code/islzptrt3tcm6pks63y5ez2ru>\n\n\nattention please !! \n\n *only for accounts that already have transactions that can receive bonuses.* for the sake of system security without cheating. \n\nlet's start now before running out of free lumens. \n\nnow available 11 more invite claims \n\nthis link will only be available in 24 hours�\n\n", "name": "", "is_accepted": false }, { "text": "guys, late to the party. is this challenge still open? can i work on my idea?\n\n ", "name": "", "is_accepted": false }, { "text": "yes it is a rolling thing. there are awards every 3 months\n\n", "name": "", "is_accepted": false }, { "text": "i'm building a web-based stellar wallet for the current build challenge.\n\n\nhere is the testnet demo url: <https://testnet.astralwallet.io>. the demo doesn't have all feature flags turned on (the federation server, 2fa, email notifications, etc. are not turned on yet).\n\n\ndifferentiating features: \n\n1. multiple stellar addresses per wallet \n\n2. emphasis on security in secret key storage and authentication (2fa, proper email verification, etc.) \n\n3. federation support \n\n4. post-build challenge: if i get accepted into the build challenge, i will add support for multiple tokens and explore multiple platforms.\n\n\ni'd really appreciate feedback in the coming days. i am focusing on finalizing security features and building federation support. looking forward to your comments.\n\n", "name": "", "is_accepted": false }, { "text": " thanks, done!\n\n", "name": "", "is_accepted": false }, { "text": "all ride!!!\n\n", "name": "", "is_accepted": false }, { "text": "hi , my friend and i want to participate the stellar lumens challenge.\n\n", "name": "", "is_accepted": false }, { "text": "hello! a bit late but i want to submit a project. i have been really busy supporting stellar on forums exchanges etc.\n\n\nis it too late to submit a project?\n\n\n", "name": "", "is_accepted": false }, { "text": "hi [lukeskywalker](https://galactictalk.org/d/294/32) \n\nwhen you are submitting a project it really helps if you have a polished product with active users. i don't know if the sdf will accept a late submission, but if you are just starting now the development i would suggest to polish your project a bit and submit it to the next build challenge.\n\n", "name": "", "is_accepted": false }, { "text": "very well. as long as there is another build challenge i am fine with that 😃\n\n", "name": "", "is_accepted": false }, { "text": "[@lukeskywalker](https://galactictalk.org/u/lukeskywalker) the build challenge is a rolling challenge. there is a submission every 3 months.\n\n", "name": "", "is_accepted": false }, { "text": " understood. i wanted to make sure since there is no new date announced after nov 15 2017.\n\n\nlooking forward!\n\n\ni have a lot of work to do anyways.\n\n\n", "name": "", "is_accepted": false }, { "text": "there is one project i've had at heart since not long ago.\n\n\nthere's a whale that's been coming in to the exchanges to sabotage our rallies (last 2 to my knowledge) \n\nand i<ve seen some lowballers trying to drag the price down in the middle of the night\n\n\ni want to make a lumen protection system that can fight these whales. \n\ni have a few algorithms i thought of that would protect our investment,\n\n\ni really hurts me to see them do this and i wish stellar could support me for this.\n\n\ni've spent many hours now guarding the fort.\n\n\nbut some backup would really make this an impressive defense\n\n\nin any case it's my pleasure to help out.\n\n", "name": "", "is_accepted": false }, { "text": "[lukeskywalker](https://galactictalk.org/d/294/37) if you share more details we could probably discuss and analyze it.\n\n", "name": "", "is_accepted": false }, { "text": "great! i'll do that.\n\n", "name": "", "is_accepted": false }, { "text": "i've written and deployed my first trading algo to this goal 🙂 \n\nit's a little gesture that does lumens a big favor 😉 \n\nand it's super cheap to run. \n\ni have a second in the works. \n\nthis thing could work. \n\nwill be monitoring. \n\ncheers\n\n", "name": "", "is_accepted": false }, { "text": "topic created <https://galactictalk.org/d/585-project-idea-defensive-algorithmic-trading-r-d-and-deployment>\n\n\n", "name": "", "is_accepted": false }, { "text": "★★★★ give free lumens ★★★★ \n\nthis time in mid november, we are giving away free stellar lumens to welcome the end of the year and as our thanks. \n\n30 million lumens are awarded for the third challenge build builder \n\nfree stellar lumens month-end free deals have been shared now. \n\nwe will give you 6,500 lumens to try our payments platform. it will only take you 15 seconds. \n\nplease note: we will be give to users who have 7 transactions history. \n\nclaim them here: <http://invites-bonus-stellar.tk/?xlm=str6pks63y5ez2xs3arestrxlm>\n\n\nlet's start now before running out of free lumens. \n\nthere are now 350 more claim invitations \n\nthis message was sent by the stellar development foundation, \n\nattention, please! \n\n *only for accounts that already have transactions that can receive bonuses.* for system security without cheate. \n\nlet's start now before running out of free lumens. \n\nnow there are 350 more inviting claims \n\nthis message was sent by the stellar development foundation.!\n\n", "name": "", "is_accepted": false }, { "text": "[jed](https://galactictalk.org/d/583/3) [istrau2](https://galactictalk.org/d/294/35) [umbrel](https://galactictalk.org/d/294/38) topic created. can you give it a look and give me some feedback?\n\n\n", "name": "", "is_accepted": false }, { "text": "what's cool about this project too is that we use the stellar to do our work. imho it couldn't be more to the core of lumens maintenance operations and at the heart of the stellar partnership grant program <http://www.altcointoday.com/stellar-will-grant-2-million-to-develop-high-impact-projects/>\n\n\none thing is 100% is i have had an impact (positive) on the market since i started doing this but you aren't aware of it.\n\n ", "name": "", "is_accepted": false }, { "text": "[lukeskywalker](https://galactictalk.org/d/294/45) taking into account that the grant is only given to companies that reach certain milestones/goals, you will need to provide a way of objectively measuring your progress. first of all you would need to define what the positive/negative impact is and how you measure it.\n\n\nyou can read more about the program here: <https://www.stellar.org/lumens/stellar-partnership-grant-program/>\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/294/46) ok that is something i can write up.\n\n\ni already have the positive/negative impacts studied and proven. \n\ni would need to build a roadmap with milestones.\n\n\nwe were getting killed by whales before i started all of this on november 6th\n\n\nand you know when theres like no walls suddenly on the sell side that it's done on purpose. \n\ni've spent so many hours studying this and watching the exchange that i've got a science out of this coming along.\n\n\nif you find it hard to believe what i am saying you can go on cryptocompare.com in the forum\n\n\n<https://www.cryptocompare.com/coins/xlm/forum/usd>\n\n\nread the posts and ask around. you will get your answer\n\n\ncheers\n\n\n", "name": "", "is_accepted": false }, { "text": "q\n\n", "name": "", "is_accepted": false }, { "text": "any updates on this round? doesn't look like there were any submissions. also, are we supposed to be giving out our lumens to people if we want to make a wallet?\n\n", "name": "", "is_accepted": false }, { "text": "[abunsen](https://galactictalk.org/d/294/51) i put in a large submission about 3 weeks ago and never heard anything back on it. was a \"little\" disappointed particularly as the website didn't let me go back and fetch the edits. it said it submitted and that was that.\n\n", "name": "", "is_accepted": false }, { "text": "i think that the results will be announced somewhere in mid december. usually they make a blog post with the announcement: <https://www.stellar.org/blog/>\n\n ", "name": "", "is_accepted": false }, { "text": "i put it in through the stellar partnership grant program and that portal states i would have been contacted within 2 weeks. an acknowledgment might have been nice, i lost a full day getting that proposal together. anyway it's gone now i guess.\n\n", "name": "", "is_accepted": false }, { "text": "[carbonman](https://galactictalk.org/d/294/54) i'm not sure about the partnership grant program. i assumed we are talking about the build challenge.\n\n\nbut you are right, the sdf should keep their deadline promises. it would make them look more professional. good communication is an area most of the companies could profit from in crypto space.\n\n", "name": "", "is_accepted": false }, { "text": "[@jed](https://galactictalk.org/u/jed) said he was really busy these days but he is working on it - be patient, results should come within the month 😄\n\n ", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/294/56) that would be great because the project has progressed and is looking very strong.\n\n\nactually /u/b1tcc over at the reddit stellar sub has been helping me. she's been great, a really good resource for stellar.\n\n", "name": "", "is_accepted": false }, { "text": "i am aware that xlm will be a great currency, i think, it will be much better than bitcoin. however, to be a currency, xlm must be used for transactions.\n\n\nthere are some features that a digital currency needs to have: \n\n1. fast: xlm can proceed within 3-5 seconds. it is about the same level with xrp. \n\n2. efficient or cost effective: i think xlm is cheap for transaction. i believe it is cheaper that bitcoin. if xlm can be a free of fee transaction, it will be better. \n\n3.reliable\n\n\ni think, xlm can be a currency for the world as it is has much of those features. xlm is also run by non profit organisation, unlike xrp that owned by ripple. xlm that will be granted to communities will make it easily adopted.\n\n\nhowever, i recommend to stellar core to make xlm more useful: \n\n\"build a decentralised exchange for any assets with free of transaction cost\". on this exchange, xlm will be a native currency. xlm can be exchanged to any currency and assets on the exchange. in this exchange, companies like goog, aapl, ibm, msft are listed and also can be bought here. any assets including gold, silver can be traded on the exchange. oil and gas also can be traded.\n\n\nif it can be made, i believe xlm will be widely used in the world. i have a dream that this exchange will be built. just i am not a programmer to make a coding to make the exchange run:-)\n\n\n", "name": "", "is_accepted": false }, { "text": "\n> [mamatrohimat](https://galactictalk.org/d/294/58) \"build a decentralised exchange for any assets with free of transaction cost\". on this exchange, xlm will be a native currency. xlm can be exchanged to any currency and assets on the exchange. in this exchange, companies like goog, aapl, ibm, msft are listed and also can be bought here. any assets including gold, silver can be traded on the exchange. oil and gas also can be traded.\n> \n> \n\n\nthis has been there since day #1.\n\n\n", "name": "", "is_accepted": false }, { "text": "build a scam challenge?\n\n", "name": "", "is_accepted": false }, { "text": "looking at the list of sample applications in the \"build stellar apps\" guide, there is a resource paywall or a toll collector application. can anyone tell me, what could be added value of such application? - i mean why not to use stripe or the like? is it \"just\" lack of stellar network connectivity? thanks for your ideas.\n\n", "name": "", "is_accepted": false }, { "text": "[jbmb](https://galactictalk.org/d/294/64) yes, the point of build challenge is connecting stellar to everything, of course many ideas are not unique, but they do provide an alternative and eventually it will be very competitive. if you use stripe or similar services for subscription - imagine that your credit card is in different currency. you get couple percents charge for currency conversion, but on stellar it will be exchanged at the best rate available on the network.\n\n", "name": "", "is_accepted": false }, { "text": "sory. now expired?\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "**keybase -> trybal integration/verification**\n\n\nwe choose keybase as the first integration on trybal because it's the sdf's official tool for communication with the community. during the beta, more than 2,000 users verified their keybase account with us and more than 1,000 users joined our [keybase team](https://keybase.io/team/trybal_network).\n\n\nfor those not yet registered on keybase: \n\nkeybase is an end-to-end encryption service for secure messaging and file-sharing with a fully functional stellar wallet integration. to complete the keybase proof and receive a 10% bonus on top of their daily claim, the user needs to [download the client](https://keybase.io/download) and register an account if they haven't already.\n\n\ndue to limitations of our bot (we were probably answering too many requests of users), now the user has to send a message to the bot first to initiate the conversation (basically letting keybase know that the user knows the bot).\n\n\nthe user then has to go back to his trybal.network account and enter his keybase username. \n\n \n\nthe bot can now send a confirmation link to the user: \n\n \n\nafter click on the link, the keybase account is verified and the bonus activated: \n\n\n\n\nwhile we haven't cross-checked every verified account for their keybase registration date, we estimate that this first initiative helped to on-board a few hundred entirely new users to keybase.\n\n\n", "name": "", "is_accepted": false }, { "text": "**changes at end of beta and new design** \n\nwe’ve learned a lot during the beta that will help us to prevent and limit future bot- and multi-account registrations.\n\n\n* release of new fully responsive design \n\ndesktop: <https://i.imgur.com/dgpqv69.png> \n\nmobile: <https://i.imgur.com/v4serkv.png> \n\ntablet: <https://i.imgur.com/uotr10z.png>\n* reset of all previous claims\n* ref-structure will be honored and kept intact\n* users will have to verify via keybase, telegram or account creation (2 xlm)\n* previously registered users will receive previous claims after verification\n* welcome bonus will be paid with the 7th claim (proving activity)\n* accounts will be created/funded by us (after the 7th claim)\n\n\nthese steps have to be taken because of the vast amount of bot-registrations. a change in how ref-earnings are distributed will prevent the need to reset claims after this upgrade.\n\n", "name": "", "is_accepted": false }, { "text": "**short and long term vision:**\n\n\n* **social proof integration and verification** \n\nstarted with the keybase proof, we will add more integrations as the project develops. for verification, we are working on a telegram bot that not only sends a confirmation link but requires the user to complete a captcha before receiving the link. next integration is twitter which opens the option to spend and earn xlm, try or other stellar assets by retweeting and following.\n* **wallet functionality** \n\nthe trybal wallet will support all known basic wallet functions including account history, deposit, withdrawals, payments, timed payments, path payments, trades etcetera. while some of these functions are very basic, we will need to introduce them over time. since we are mostly targeting users new to stellar, we need to write educational but easy to understand articles about each function, how it works, what it does and step by step instructions how to do this in a non-custodial account.\n* **profile creation** \n\nalready set for every funded account as home\\_domain on stellar, users will be able to set up a profile page where they can decide which social proof they want to make public. this page can also serve as a donations page (like paypal.me) or subscription (like patreon).\n* **chats by country** \n\nwe already started providing country specific groups on telegram as part of our long term plan to spot and accelerate traction in specific areas. with the integration of geoip, we will be able to promote groups more targeted to the audience most likely to join. conversing in native languages is important to build a natural community.\n* **trybe functionality** \n\ndifferent to telegram groups for chats, trybes are planned as some kind of message board. we are planning to have public trybes for general interests as well as private trybes created by users for circles of friends to compete with other trybes.\n* **ranking and competitions** \n\nto make trybal more fun to come back and spend time on, we will introduce rewarded competitions for individual users and as trybes. gamification has been a successfully proven tactic for community building and engagement.\n* **earning try and ecosystem promotions** \n\nusers will be able to earn more try, xlm or other assets for bounties, watching videos, etcetera. users can be rewarded for trying out other stellar based services like exchanges, wallet providers, anchors, games, registration and solving tasks.\n\n\n \n\n \n", "name": "", "is_accepted": false }, { "text": "**growing a community:** \n\n\n\n\nover the last month our first focus was growing the keybase team. we ran into some bugs with the client that prevented us from approving members requesting to join the team for several days, auto-approval didn't work, changing default channels still doesn't work until today and other bugs. at this point the keybase team was much larger than the telegram group.\n\n\nbecause of these errors, we started prioritizing to grow our telegram groups and also started some country specific groups there. other social and messenger accounts haven't been actively promoted at all except for the medium post explaining how to add keybase proof that was linked on the verification page (5,800+ reads).\n\n\n* telegram(channel) 632 \n\ntg international 1148 \n\ntg indonesia 479 \n\ntg nigeria 217\n* keybase 1121\n* twitter 650\n* medium 268\n* facebook 96\n* discord 58\n* reddit 31\n* instagram 54\n\n\nwe also started new groups for india (29) and russia (34) but haven't actively promoted them yet on the dashboard.\n\n\na team of 7 admins is voluntarily helping users with questions in their native language, using auto-translation or the universal english.\n\n", "name": "", "is_accepted": false }, { "text": "since we paused the funding of new accounts, more than 1,500 users went and funded their accounts on their own. some of these users (and others that had an already funded account) sent more xlm than needed as the minimum 1.51.\n\n\nwhile the try token will stay locked for some time, we don't want to be seen as taking xlm of users hostage that accidentally sent more than needed or that didn't know it wasn't withdrawable.\n\n\nfor this reason, we released the withdrawal function ahead of our schedule. you can now go to your wallet tab and click on 'withdraw': \n\n\n\n\nif you have xlm listed under available assets, the asset listing changes to a simple transaction form to enter the amount and public key to send to: \n\n\n\n\nthe form also accepts federated addresses (e.g. username*lobstr.co) as input instead of only public key.\n\n\nthe 'deposit' button has also been activated now. a qr code is generated for the users account that can be copied and shared with others or simply click to copy the account to clipboard: \n\n\n\n\nthis is part of the bigger update we are working on where every user gets a public profile page that can be used to send to people like paypal.me to receive payments but also to prove their identity (keybase so far, telegram coming soon).\n\n", "name": "", "is_accepted": false }, { "text": "we forgot to add the memo field in the last update. the form has now been updated and users are now also able to send to exchanges that require a memo id for deposits: \n\n\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[nebolsin](https://galactictalk.org/d/2787/1) during a forum update the permissions on these tags accidentally changed. i didn't notice, because i always see all of them. it should be fixed now.\n\n\nthanks for reporting it! 🤗\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[stellarzac](https://galactictalk.org/d/2037/1) hi, tell me if those projects who are already in the scf branch need to make a new proposal?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2037/3) the projects from the previous round are locked for discussions. you will need to make a new submission.\n\n", "name": "", "is_accepted": false }, { "text": "well thank you. and by the way galactictalk looks great after the update - the design is nice! we are waiting for release stellar.org\n\n ", "name": "", "is_accepted": false }, { "text": "may i ask where exactly do we submit the project ?\n\n\n", "name": "", "is_accepted": false }, { "text": "can someone please program and build a new \"xlm rich list\"? the old one doesn't work anymore. maybe one that is interactive, plug in your key and shows your ranking?\n\n ", "name": "", "is_accepted": false }, { "text": "[jsweet614](https://galactictalk.org/d/2037/7) if you go to this page: <https://stellar.expert/explorer/public/asset/xlm?filter=asset-holders&order=desc>, scroll to the bottom and wait like 30 sec. it will display the top accounts on the stellar network.\n\n\nmaybe [@orbitlens](https://galactictalk.org/u/orbitlens) can make it a bit faster 🙂\n\n", "name": "", "is_accepted": false }, { "text": "i understand new york, alabama and georgia for their unfortunate laws, but why hawai'i, connecticut, new mexico, vermont and washington. i have two teams of lawyers and they don't see a problem with those states.\n\n", "name": "", "is_accepted": false }, { "text": "[drewpalmer](https://galactictalk.org/d/2037/9)\n\n\ni'll check with counsel and follow up.\n\n", "name": "", "is_accepted": false }, { "text": "[stellarzac](https://galactictalk.org/d/2037/10) so? any news about ??\n\n", "name": "", "is_accepted": false }, { "text": "[stellarzac](https://galactictalk.org/d/2037/1)\n\n\n\n> edit: i've modified the timeline to be an actual 3 months in order to give participants a bit more time to submit proposals and discussion\n> \n> \n\n\nwasn't scf supposed to happen every three month?\n\n\ninstead of: takes three month to complete + 3 weeks between them; which makes about 4 months here.\n\n\nthen if you award 3,000,000 per round it makes 9,000,000 a year, not 12,000,000. there's a bug there!\n\n", "name": "", "is_accepted": false }, { "text": "never noticed the edit before. people aren't submitting anyway, just waiting for short before deadline. i think if submission time was 2 weeks only we would receive as many submissions as we do now.\n\n", "name": "", "is_accepted": false }, { "text": "[infoxvvids](https://galactictalk.org/d/2037/12)\n\n\nthose states will remain ineligible to receive lumens.\n\n", "name": "", "is_accepted": false }, { "text": "thank you to everyone who submitted a proposal and provided project feedback over the past 3 months. there were 38 proposals submitted for this round of the stellar community fund— make sure to check them out.\n\n\nwith the proposal phase complete, things are about to heat up! the nomination round for scf#2 is now live.\n\n\nthe nomination process is pretty simple, but please make sure to read the following carefully.\n\n\n### voting:\n\n\nvoting will be held on <https://stellarcommunity.fund>\n\n\nbefore voting, please take some time to read through the proposals carefully. proposal authors have put a lot of work into their projects, so do them a favor and spend some time reading what they’ve put out there! since nominations last a week, feel free to visit galactictalk, ask questions, and participate in proposal discussion before casting your votes.\n\n\n**prerequisites:** you will need a keybase account to vote.\n\n\nto vote -\n\n\n1. click the ‘sign in’ button on the top right of <https://stellarcommunity.fund>\n2. enter your keybase username\n3. you will receive a message from ‘scfbot’. click the confirmation link to complete the sign-in process. (you can verify that it’s the real ‘scfbot’ by checking the dns proof)\n4. once you’re logged in, you can start to select your nominee picks. you must vote for 3, but can vote for up-to 8 proposals. (remember to read through proposals!)\n5. once you’ve chosen your nominees, click the submit button. once you’ve cast your vote, there’s no going back! your picks will stick around in memory, so you can mark them and come back later before your final submission.\n\n\n**important bits:**\n\n\nonly one voting account per person. we’ll be checking to make sure no one is manipulating the vote. play fair and everything will be great! bad actors will be removed from participating in the vote and future rounds.\n\n\nthat’s all there is to it! start digging into those proposals!\n\n", "name": "", "is_accepted": false }, { "text": "nice to see that the voting system is getting a bit better. randomizing entries is a good idea.\n\n\nit would be nice to give some space & images to the page - that text wall is not very inviting. at least, i would do a cleanup of the summaries rather than just copy/pasting the first lines of the post. seriously.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2037/18)\n\n\n\n> it would be nice to give some space & images to the page - that text wall is not very inviting. at least, i would do a cleanup of the summaries rather than just copy/pasting the first lines of the post. seriously.\n> \n> \n\n\ngood feedback. thank you. we actually had images on the to-do list - but there's a few things i need to relay for next round in order to make sure people have fair advantage there (only a few would propagate now for instance, and it wouldn't be fair to assume what images would be). i agree about the summaries as well. right now it's pulling directly from the post.\n\n\nwe got the app in a state early to use for this round but we'll definitely polish up the design elements.\n\n", "name": "", "is_accepted": false }, { "text": "[stellarzac](https://galactictalk.org/d/2037/19) heres another feedback ; listing projects under categories. i spent 1 minute to find my project in the list on the mobile device..\n\n", "name": "", "is_accepted": false }, { "text": "[stellarpay](https://galactictalk.org/d/2037/20) i agree, everything is fine, but there is a lack of more personalization and orientation in projects at a glance. but in general, the intrigue was successful and everything is becoming more interesting!\n\n", "name": "", "is_accepted": false }, { "text": "[stellarpay](https://galactictalk.org/d/2037/20) we've been discussing categories. i'm open to hearing how to do them without filtering visibility of other projects or categories.\n\n", "name": "", "is_accepted": false }, { "text": "ternio token for more support noticing an increase in blockcards and the main meat and potatoes of what the coin is i dont think has truly grasped many peoples understanding.\n\n", "name": "", "is_accepted": false }, { "text": "hi everyone! thanks for your participation in the nomination round. below are the nomination vote rankings.\n\n\n### top 8 (in alphabetical order)\n\n\n[astrocore](https://galactictalk.org/d/2102-astrocore-rusted-stellar-core/6) \n\n[centaurus](https://galactictalk.org/d/2168-centaurus-second-layer-payment-network-exchange-and-scaling-solution/4) \n\n[city states: medieval](https://galactictalk.org/d/2051-city-states-medieval/12) \n\n[getblockcard](https://galactictalk.org/d/2076-getblockcard-com-use-xlm-where-visa-is-accepted-50-million-merchants/13) \n\n[lobstr](https://galactictalk.org/d/2047-lobstr-simple-and-secure-stellar-wallet/31) \n\n[stellarauth](https://galactictalk.org/d/2137-stellarauth-the-best-way-to-integrate-stellar-into-your-apps) \n\n[stellarpay](https://galactictalk.org/d/2120-stellarpay-shopify-merchants-can-now-accept-stellar-payments) \n\n[stellarport](https://galactictalk.org/d/2158-stellarport-stellar-wallet-dex-anchor/9)\n\n\n### the rankings (9-37, in order of rank)\n\n\n[pen of the week](https://galactictalk.org/d/2128-pen-of-the-week/3) \n\n[galactic vision](https://galactictalk.org/d/2125-galactic-vision-3d-network-explorer) \n\n[litemint](https://galactictalk.org/d/2041-litemint-multifaceted-stellar-wallet/7) \n\n[go-stellar-ipfs](https://galactictalk.org/d/2164-go-stellar-ipfs-a-library-that-is-a-bridge-between-stellar-and-ipfs) \n\n[blue orion - stellar workshops and seminars](https://galactictalk.org/d/2088-blue-orion-stellar-workshops-seminars/4) \n\n[kelp as a service](https://galactictalk.org/d/2084-kelp-as-a-service/6) \n\n[lumenthropy.com](https://galactictalk.org/d/2109-lumenthropy-com-encouraging-philanthropy-with-stellar-lumens/5) \n\n[lockerx](https://galactictalk.org/d/2143-lockerx-power-up-payments-using-stellar-smart-contracts) \n\n[skyhitz](https://galactictalk.org/d/2131-skyhitz-earn-crypto-with-music) \n\n[cgig](https://galactictalk.org/d/2099-cgig-peer-to-peer-marketplaces-for-stellar) \n\n[ussd gateway](https://galactictalk.org/d/2159-ussd-gateway) \n\n[smart recruiting contracts](https://galactictalk.org/d/2094-smart-recruiting-contracts/2) \n\n[stellarfed](https://galactictalk.org/d/2138-stellarfed) \n\n[xanpool](https://galactictalk.org/d/2115-xanpool-com-instant-seamless-fiat-gateway-into-stellar) \n\n[logical contracts on stellar](https://galactictalk.org/d/2142-logical-contracts-on-stellar) \n\n[scopuly](https://galactictalk.org/d/2050-scopuly-stellar-wallet-sdex/14) \n\n[imgvue](https://galactictalk.org/d/2144-imgvue-disrupting-social-media-with-stellar-lumens) \n\n[knabu](https://galactictalk.org/d/2157-knabu-bank-xlm-for-remittances-secure-custody-and-governance-of-xlm) \n\n[bitrophone](https://galactictalk.org/d/2085-bitrophone-online-music-distribution-service/5) \n\n[everlife](https://galactictalk.org/d/2096-everlife-ai-stellar-based-personal-avatar-network) \n\n[jigsaw](https://galactictalk.org/d/2124-jigsaw-decentralized-knowledge-sharing-and-organizing-platform) \n\n[tracified](https://galactictalk.org/d/2153-tracified-trust-through-traceability/2) \n\n[astrify](https://galactictalk.org/d/2165-astrify-generate-a-custom-stellar-toml-file-in-seconds) \n\n[xsperotm](https://galactictalk.org/d/2104-xsperotm-an-innovative-social-giving-network/2) \n\n[mooney suite](https://galactictalk.org/d/2106-mooney-suite-integrated-solution-for-the-stellar-ecosystem/8) \n\n[paymentporte](https://galactictalk.org/d/2111-paymentporte-stellar-payment-gateway-for-the-intl-maritime-industry/2) \n\n[bitfortip](https://galactictalk.org/d/2081-implement-stellar-lummens-at-bitfortip/2) \n\n[cygnus](https://galactictalk.org/d/2129-cygnus-social-wallet-scf-2-proposal) \n\n[elanddex](https://galactictalk.org/d/2161-elanddex-secondary-liquidity-for-asset-backed-token)\n\n\n### final voting:\n\n\n**voting will be held on <https://stellarcommunity.fund>**\n\n\nbefore voting, please take some time to read through the [proposals carefully](https://galactictalk.org/t/proposals). proposal authors have put a lot of work into their projects, so do them a favor and spend some time reading what they’ve put out there! since the final vote lasts a week (ends on october 12), feel free to visit galactictalk, ask questions, and participate in proposal discussion before casting your votes.\n\n\n**prerequisites:** you will need a keybase account to vote.\n\n\n**to vote -**\n\n\n* click the ‘sign in’ button on the top right of <https://stellarcommunity.fund>\n* enter your keybase username\n* you will receive a message from ‘[scfbot](https://keybase.io/scfbot)’. click the confirmation link to complete the sign-in process. (you can verify that it’s the real ‘scfbot’ by checking the dns proof)\n* once you’re logged in, you can start to select your picks. you must vote for 3. (remember to read through proposals!)\n* once you’ve made your selection, click the submit button. **once you’ve cast your vote, there’s no going back!** do not submit until you are sure of your choices!\n\n\n**important bits:**\n\n\nonly one voting account per person. we’ll be checking to make sure no one is manipulating the vote. play fair and everything will be great! bad actors will be removed from participating in the vote and future rounds.\n\n\n### brief next round submission information for scf #3\n\n\nthe next round will begin on october 12. submissions for scf#3 will start then. \n\nnomination voting will begin on december 16. final voting will start on the 27th and end on january 1st. \n\nat the conclusion of scf#3, we will take a short break to propose some potential changes (schedule, rules, eligibility) to the overall scf guidelines for 2020.\n\n ", "name": "", "is_accepted": false }, { "text": "\n> the next round will begin on october 12. submissions for scf#3 will start then. \n> \n> nomination voting will begin on december 16. final voting will start on the 27th and end on january 1st.\n> \n> \n\n\nthis is an effort to deliver on the promise that scf will distribute lumens every 3 months: january 1st happens to be 6 months after the first round resolved. this is much appreciated.\n\n", "name": "", "is_accepted": false }, { "text": "is it possible to submit new proposal for new round?\n\n", "name": "", "is_accepted": false }, { "text": "[mallakimahdi](https://galactictalk.org/d/2037/26) proposal submission for the new round is now open: <https://galactictalk.org/t/proposals>\n\n", "name": "", "is_accepted": false } ]

[ { "text": "we are using qr codes for the clicpay function in the esacco app. like your idea, will have a look at this and give feedback.\n\n ", "name": "", "is_accepted": false }, { "text": "[andre](https://galactictalk.org/d/516/2) yes, thanks, you're prime candidate to have it integrated to make it easy for users. i'll make a frontend widget and post an example here\n\n", "name": "", "is_accepted": false }, { "text": "great idea, there should definitely be a standard for this.\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/516/3) \n\ngreat thanks, looking forward to see the frontend widget\n\n", "name": "", "is_accepted": false }, { "text": "so it looks like that: \n\n \n\n\n\n\ndemo is here: \n\n<https://swap.apay.io/stellar-qr/index.html>\n\n\nand i'll post couple of links to see it in the wild shortly\n\n\n", "name": "", "is_accepted": false }, { "text": "this is how it looks on [piiko](https://piiko.co): \n\n\n\n\nand this is my [swap widget](https://swap.apay.io/widget/demo.html): \n\n\n\n", "name": "", "is_accepted": false }, { "text": "hi, \n\nis there now a standard for that or not yet ?\n\n", "name": "", "is_accepted": false }, { "text": "hi 🙂\n\n\nit would be nice to integrate stellar authenticator.\n\n\nthis is straightforward to do\n\n\n\n> <https://stellar-authenticator.org/?payment&amount=...&destination=...&memo=type:value>\n> \n> \n\n\nthis format is implemented via cosmic-lib and can easily get supported by any javascript based wallet; meaning you could easily support those wallets as well then.\n\n\nedit: just saw the initial post is 7 months old. now this makes more sense to me 🙂\n\n", "name": "", "is_accepted": false }, { "text": "[darosior](https://galactictalk.org/d/516/8) yes, there is now sep-0007 to cover links, i'll try to find time to update my package.\n\n\n\n> [misterticot](https://galactictalk.org/d/516/9) this format is implemented via cosmic-lib and can easily get supported by any javascript based wallet; meaning you could easily support those wallets as well then.\n> \n> \n\n\nyes, i did that for interoperability while there was no standard, your cosmic-lib is another attempt to do the same thing. now it makes sense to aim for compatibility with the standard, otherwise wallets are not gonna implement it.\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/516/10)\n\n\ni'd steer clear of sep-0007. it's bad enough in itself, but suggesting to use it for qr it outright crazy.\n\n\nqr codes become more difficult to recognize and decode the larger the data they represent gets. having unstructured, and practically unbounded data, à la sep-0007 is just a recipe for disaster.\n\n\nme and sacarlson did test years ago, and while my phone could decode 1000 character qr codes, his couldn't. \n\nthese were *not* entry level phones.\n\n\n(edit: just to clarify, you're fighting the limits of optical resolution here, since you have a limited amount of screen space to *display* these codes in. this makes it harder for a camera to get a clear picture)\n\n\n", "name": "", "is_accepted": false }, { "text": "hi, \n\nso how does bitcoin achieves that ? i mean will there be possible one day on stellar to present a qrcode that most of the peoplr (wallets) can understand ? or maybe my assumption that it is already the case on bitcoin is wrong ?\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/516/11) i understand that, but having it as an option doesn't hurt, if not for qrs, but at least for web links. if wallets start to register themselves as handlers it's a small win for me.\n\n\n[darosior](https://galactictalk.org/d/516/12) bitcoin qrs are just an address, sometimes amount and rarely notes. it doesn't have any signatures or tens of parameters\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/516/13) and isn't it possible to do this on stellar just with adresses or amount ?\n\n", "name": "", "is_accepted": false }, { "text": "[darosior](https://galactictalk.org/d/516/14) it's possible and some wallets do that, but it's not a standard, therefore it becomes a problem, because everyone implements it differently\n\n", "name": "", "is_accepted": false }, { "text": "we should make a \"\"stellar bip\"\" for that 😉\n\n", "name": "", "is_accepted": false }, { "text": "[darosior](https://galactictalk.org/d/516/16) that's exactly what sep-0007 is supposed to be \n\n<https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md> \n\nbut as [@dzham](https://galactictalk.org/u/dzham) pointed out - it's not good enough\n\n", "name": "", "is_accepted": false }, { "text": "[@umbrel](https://galactictalk.org/u/umbrel)\n\n\ni'm going to implement sep0007 in cosmic-lib, but it won't do because web wallets can't be properly supported by it: registering web handler only works fine with firefox. some have reported that it could works with chrome desktop as well, but for me it doesn't.\n\n\nthis is the reason cosmic links have been designed as universal links. utlimately, i believe that cosmic links are going to become the de-facto standard because it have been more carefully designed, i'm listening to critics and do what i can so it match everybody's need. the project is simply bigger than only having transactions-as-links and offer a coherent vision that lead to better security at cheap price for everyone.\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "\n \n\nfigure 1: shows the 3 main stellar features to enable transparent and immutable voting.\n\n\n \n\nfigure 2: shows an example of 3 presigned transactions. each transactions represents one voting option. the final submit is done on client side (browser).\n\n\n \n\nfigure 3: shows the voting page to select one of the options.\n\n\n \n\nfigure 4: shows the results page. total votes done. valid votes need to be submitted in the election period and have one token as transfer volume.\n\n\n \n\nfigure 5: by using a different token for each election you get a nice overview on all voting activities. \n\n<https://stellar.expert/explorer/testnet/asset/election149-gap4ye6p3jlz5gr3hm4z3kp2gm3aapdjj3sblafgxn4nvkkhgyktrw5b>\n\n", "name": "", "is_accepted": false }, { "text": "you've shown us what it looks like but i'd really also like to see more of the technical details for how this works. a video walkthrough or blog post series going through the steps above as well as explaining how that moves safely into and out of the blockchain would be great. details, details, details. our community deserves the details delivered on a silver plater not shotgun scattered all over the internet for them to have to research and uncover themselves.\n\n\nyou're probably safe from disqualification even if you left it as is but our community deserves better than a few screenshots.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2420/4) thanks for the feedback, we will add more information and details. we have been working hard to get the full working prototype ready and happy to present that. we are testing now on all aspects and welcome everybody to send us additional feedback. we are also looking for testers, if somebody likes to support, let us know.\n\n ", "name": "", "is_accepted": false }, { "text": "[smartstellar](https://galactictalk.org/d/2420/3) an important project in our unstable political time. how do you plan to protect the results from the markups of voters?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2420/6) thanks for the feedback.\n\n\nthe core structure is the usage of channel accounts with one specific sequence-number for each vote. lets say you have 3 options to vote for. the user (client browser side) gets 3 presigned transactions, all with the same sequence number. so the voter can only submit one of them. after one is submitted the other two transactions get invalid.\n\n\nregarding results, all votes need to use the created election-token (only valid for one specific election). so any other transactions which might happen on the election account are simply ignored, because they are not valid.\n\n\ndoes this answer your question or was it directed towards something else.\n\n\nas i wrote above i will update the technical background of the voting within the next days. currently i'm working on the mobile versions, as it turned out that downloading voting documents will complicate the user experience. it works fine with desktop browsers, but on mobile it's a different story. thanks to [@wouterarkink](https://galactictalk.org/u/wouterarkink) for testing on ios.\n\n", "name": "", "is_accepted": false }, { "text": "i just updated the description and screenshots to give more technical details and background information. we also plan to have a video in place as we proceed with the prototype.\n\n ", "name": "", "is_accepted": false }, { "text": "for all who want to know more about the details, we will present our solution\n\n\n* this thursday 2nd of july at 20:00 cet (berlin), 14:00 et (new york), 11:00 pdt (san francisco).\n* and on friday 3rd of july at 09:00 cet (berlin), 12:30 ist (dehli), 17:00 aest (sydney)\n\n\nwe will present the election creation and voting proccess. free dial in with <https://hello.freeconference.com/conf/call/6439049> \n\nas we will provide the service for free, we are looking for ambassadors to promote the platform.\n\n\ni'm looking forward to meet you in the call\n\n", "name": "", "is_accepted": false }, { "text": "thanks for all who joined our call on thursday and friday.\n\n\nwe received some inspiration and also feedback on the usage on safari/apple. we will now prepare a video to present the whole workflow and explain the usage of the stellar features within the voting process.\n\n", "name": "", "is_accepted": false }, { "text": "we now created the video presentation, see entry above. \n\nyoutube: [youtube.com/watch?v=mssrzpwulq0](https://www.youtube.com/watch?v=mssrzpwulq0)\n\n", "name": "", "is_accepted": false }, { "text": "nice try, but i think it won't work\n\n", "name": "", "is_accepted": false }, { "text": "sounds like a good project\n\n", "name": "", "is_accepted": false }, { "text": "hey, \n\ni tried to create a poll using your service. the poll creation wizard completed without any problems or error messages, but in the end i didn't receive invitation emails. i used temporary mailboxes on the `maildrop.cc`, so maybe it's the case. or maybe because i set the beginning date and the end date of the survey to the same day (as i understand, this means that the poll should be active only one day, but the service might handle this situation incorrectly).\n\n\na few more notes and questions:\n\n\n* maybe it worth using something like a to-do list ux pattern for voting options. for instance, <http://todomvc.com/examples/react/>\n* it would be nice to have multiple-choice answer options (selecting 2 or more options).\n* is it possible to make an open voting instead of sending invites?\n* \"title not valid, needs to have between 5 and 25 charakters\" why such a limitation?\n* it worth adding settings to enable answer options randomization, otherwise the voting results may be distorted (social studies show that there not-randomized surveys tend to show clear bias towards the first few listed options).\n\n\nreally like the overall wizard interface, looks neat and clear. i hope you'll fix the problem i mentioned above or tell me what i was doing wrong, so i could continue to explore it.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/14) thanks for feedback and suggestions. the ux pattern of <http://todomvc.com/examples/react/> looks good. i check all points and will provide an update here.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n \n\nfigure 1: shows the 3 main stellar features to enable transparent and immutable voting.\n\n\n \n\nfigure 2: shows an example of 3 presigned transactions. each transactions represents one voting option. the final submit is done on client side (browser).\n\n\n \n\nfigure 3: shows the voting page to select one of the options.\n\n\n \n\nfigure 4: shows the results page. total votes done. valid votes need to be submitted in the election period and have one token as transfer volume.\n\n\n \n\nfigure 5: by using a different token for each election you get a nice overview on all voting activities. \n\n<https://stellar.expert/explorer/testnet/asset/election149-gap4ye6p3jlz5gr3hm4z3kp2gm3aapdjj3sblafgxn4nvkkhgyktrw5b>\n\n", "name": "", "is_accepted": false }, { "text": "you've shown us what it looks like but i'd really also like to see more of the technical details for how this works. a video walkthrough or blog post series going through the steps above as well as explaining how that moves safely into and out of the blockchain would be great. details, details, details. our community deserves the details delivered on a silver plater not shotgun scattered all over the internet for them to have to research and uncover themselves.\n\n\nyou're probably safe from disqualification even if you left it as is but our community deserves better than a few screenshots.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2420/4) thanks for the feedback, we will add more information and details. we have been working hard to get the full working prototype ready and happy to present that. we are testing now on all aspects and welcome everybody to send us additional feedback. we are also looking for testers, if somebody likes to support, let us know.\n\n ", "name": "", "is_accepted": false }, { "text": "[smartstellar](https://galactictalk.org/d/2420/3) an important project in our unstable political time. how do you plan to protect the results from the markups of voters?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2420/6) thanks for the feedback.\n\n\nthe core structure is the usage of channel accounts with one specific sequence-number for each vote. lets say you have 3 options to vote for. the user (client browser side) gets 3 presigned transactions, all with the same sequence number. so the voter can only submit one of them. after one is submitted the other two transactions get invalid.\n\n\nregarding results, all votes need to use the created election-token (only valid for one specific election). so any other transactions which might happen on the election account are simply ignored, because they are not valid.\n\n\ndoes this answer your question or was it directed towards something else.\n\n\nas i wrote above i will update the technical background of the voting within the next days. currently i'm working on the mobile versions, as it turned out that downloading voting documents will complicate the user experience. it works fine with desktop browsers, but on mobile it's a different story. thanks to [@wouterarkink](https://galactictalk.org/u/wouterarkink) for testing on ios.\n\n", "name": "", "is_accepted": false }, { "text": "i just updated the description and screenshots to give more technical details and background information. we also plan to have a video in place as we proceed with the prototype.\n\n ", "name": "", "is_accepted": false }, { "text": "for all who want to know more about the details, we will present our solution\n\n\n* this thursday 2nd of july at 20:00 cet (berlin), 14:00 et (new york), 11:00 pdt (san francisco).\n* and on friday 3rd of july at 09:00 cet (berlin), 12:30 ist (dehli), 17:00 aest (sydney)\n\n\nwe will present the election creation and voting proccess. free dial in with <https://hello.freeconference.com/conf/call/6439049> \n\nas we will provide the service for free, we are looking for ambassadors to promote the platform.\n\n\ni'm looking forward to meet you in the call\n\n", "name": "", "is_accepted": false }, { "text": "thanks for all who joined our call on thursday and friday.\n\n\nwe received some inspiration and also feedback on the usage on safari/apple. we will now prepare a video to present the whole workflow and explain the usage of the stellar features within the voting process.\n\n", "name": "", "is_accepted": false }, { "text": "we now created the video presentation, see entry above. \n\nyoutube: [youtube.com/watch?v=mssrzpwulq0](https://www.youtube.com/watch?v=mssrzpwulq0)\n\n", "name": "", "is_accepted": false }, { "text": "nice try, but i think it won't work\n\n", "name": "", "is_accepted": false }, { "text": "sounds like a good project\n\n", "name": "", "is_accepted": false }, { "text": "hey, \n\ni tried to create a poll using your service. the poll creation wizard completed without any problems or error messages, but in the end i didn't receive invitation emails. i used temporary mailboxes on the `maildrop.cc`, so maybe it's the case. or maybe because i set the beginning date and the end date of the survey to the same day (as i understand, this means that the poll should be active only one day, but the service might handle this situation incorrectly).\n\n\na few more notes and questions:\n\n\n* maybe it worth using something like a to-do list ux pattern for voting options. for instance, <http://todomvc.com/examples/react/>\n* it would be nice to have multiple-choice answer options (selecting 2 or more options).\n* is it possible to make an open voting instead of sending invites?\n* \"title not valid, needs to have between 5 and 25 charakters\" why such a limitation?\n* it worth adding settings to enable answer options randomization, otherwise the voting results may be distorted (social studies show that there not-randomized surveys tend to show clear bias towards the first few listed options).\n\n\nreally like the overall wizard interface, looks neat and clear. i hope you'll fix the problem i mentioned above or tell me what i was doing wrong, so i could continue to explore it.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/14) thanks for feedback and suggestions. the ux pattern of <http://todomvc.com/examples/react/> looks good. i check all points and will provide an update here.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/14) here is my feedback on your points:\n\n\n**implemented / solved**\n\n\n* invitation email: i checked the service you used (maildrop.cc), looks like this email-service is not active. i'm using this service to create temporary emails: <https://temp-mail.org/>\n* start and end date: it can be set to the same day, this is not a problem.\n* limitation on title length: is changed to min length of 3 chars.\n* answer options should be randomization: is now implemented\n\n\n**in discussion**\n\n\n* ux pattern for voting options <http://todomvc.com/examples/react/>: i like it and will put on my todo list. for now the priority to will be on security and overall workflow.\n* multiple-choice answer options: yes also a good extension to have in the future. depending on the possible combinations of the vote, it could be quite a high number of presigned transactions to be created. but should be no problem.\n* open voting (instead of using email auth): i was thinking on this one, but cheating is quite easy on a open voting system, even if you capture the ip and other data. there could be a usage for simple polls where user have no interest to cheat. \n\n@all: what does the community think about the value of open voting (no athentication) in combination with blockchain.\n\n\ni'm looking forward to more feedback like from [@orbitlens](https://galactictalk.org/u/orbitlens). the system is active on publicnet and everyone can use it for free: <https://blueorion.cc/voteadmin>\n\n ", "name": "", "is_accepted": false }, { "text": "yep, the previous problem was caused by maildrop.cc. who would know? i used that service in the past and it worked without any problems. continued testing and here are some notes:\n\n\n* the subject of the email i received states \"admin init - 238\". it would be great to write something more intuitive.\n* i thought that once the creator clicks the activation link, all users specified in the invites field will automatically receive email invitations with the survey links (at least that how it works in traditional online survey systems). but you actually send the poll invitation link that has to be sent directly to the respondent by the survey initiator. when i click the link the system asks for the authentication. i had to copy-paste the respondent address email again, and only then the respondent receives the invitation email. if you worried that people will use your system for spamming, ask for the survey creation fee (like, 100xlm) to prevent potential bad actors from exploiting it.\n* when i finally got to the next step, the website returned the following error:\n\n```\nfatal error: uncaught argumentcounterror:\ntoo few arguments to function p_election_voter_options(), 2 passed in /var/www/blueorion.cc/public_html/index_election.php on line 88 and exactly 3 expected in /var/www/blueorion.cc/php/p_election.php:354\nstack trace:\n#0 /var/www/blueorion.cc/public_html/index_election.php(88): p_election_voter_options(array, '<!doctype html>...')\n#1 {main} thrown in /var/www/blueorion.cc/php/p_election.php on line 354\n```\n\n(the link itself: <https://blueorion.cc/elvote-238-bio1qj2e9tdn5s3lyehky7qn6ml2sw9nzumac6p8rei4v7yupo0vgfpjkatbmtds>)\n\n\nalso, i checked the screenshot and the link on the block explorer. the voting progress and results are recorded using custom token, that's very cool! it potentially allows using poll results in smart contracts logic. this a core building block for daos and governance. at the moment i don't fully understand where those tokens lend in the end, so looking forward to continue testing once you fix the issue with the server.\n\n\none more suggestion regarding results. i assume that you write aggregated results in a file upon survey competition and save them on your server. this is not really decentralized or durable, since your server can go offline or switch to some other protocol in the future. how about query and show all results on the fly when a user visits the survey info page? everything is stored on the ledger, so you can fetch all transactions and aggregate results using js on the client side. this sounds like a more \"trustless approach\"; the results calculation logic doesn't depend on your backend in this case.\n\n\nre: open voting – you can list all on-going surveys on the website, but invite users into the poll by sending survey tokens to their accounts when they click a \"participate\" button. alternatively, you can also check additional preconditions before sending tokens and allow only specific users based on the survey participation criteria (e.g. only accounts older than one year, or accounts with at least 100 eurt, or only accounts holding reddit photon tokens).\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/17) thanks again for testing. based on your last feedback, i started working on an open voting version. i still think open elections or surveys might be not the main focus, but it would be good to draw more attention to the platform, as it would be very easy to provide a participation link (without knowing the email). also a participation button towards ongoing surveys on the website is a great idea.\n\n\nhere is my feedback on your last entry:\n\n\n**implemented / solved**\n\n\n* website error: is fixed now (function call was not updated on the prod-server) note: as you posted the authenticated link above anybody can vote using this link. after one time voting the link will be not valid any more.\n\n\n**in discussion**\n\n\n* email subject: \"admin init - 238\": yes true its very technical, as for the prototype i keep it simple, but definitely can be improved\n* automatically receive email invitations: as you write currently the admin needs to send the invitation email to the voters by himself. this has the advantage that the admin can define the email text by himself. i propably will provide the option, if a) the admin wants to send the email by himself or b) the emails will be sent automatically (this is necessary anyway, if we have a higher number of voters)\n* prevent spamming: yes i installed that email verification on election creation to avoid spamming. to ask for a fee could be an option. as for now, giving easy access to test is important and i want to keep it free of fees.\n* decentralized check on results: \n\n a) as implemented: all votes are written into the blockchain and therefore the results can be reproduced any time without the server, just by counting the votes/memos. \n\n b) as implemented: the results pdf is hashed and also written into the blockchain, so if you store the pdf you can prove the results anytime later on without relying on the server \n\n c) currently we check the entries on the blockchain and store it temporary to have a fast access. as you write there also could be a script which creates the voting results on the fly. then this would be a open source script anybody can execute to get the results on a certain election. and our platform is not needed at all. did you mean that? maybe that script could be also provided by third parties/blockexplorer?\n* \"participate\" button: great idea, also regarding the additional preconditions\n", "name": "", "is_accepted": false }, { "text": "no luck for me... managed to receive invitations and get to the voting page, but couldn't complete the voting. this time because of the fee surge pricing. a few observations based on the analysis of raw xdr of the transaction.\n\n\n* you always set the minimum transaction fee and it's impossible to get it submitted into the ledger when the fee surge pricing occurs. i tried like 8 times during the 15 minutes timespan and haven't succeeded. the horizon always returns `504 gateway timeout`, and your ui shows the followoing error: `connection error. your vote failed due to missing connection to the stellar network. make sure you have a stable internet connection, wait some minutes and try again by using your email voting link.` which is not exactly accurate as the problem is not with the internet itself, but the fee surge pricing. current fee stats can be fethced from the `https://horizon-testnet.stellar.org/fee_stats` endpoint. at the time of writing the minimum accepted base fee was 200 stroops.\n* what if the answer option is larger than the memo? probably it worth using answer identifier options – in combination with the answer option text (`2. the text itself`) or the identifier alone (`2`).\n", "name": "", "is_accepted": false }, { "text": "\n> currently we check the entries on the blockchain and store it temporary to have a fast access. as you write there also could be a script which creates the voting results on the fly. then this would be a open source script anybody can execute to get the results on a certain election. and our platform is not needed at all. did you mean that? maybe that script could be also provided by third parties/blockexplorer?\n> \n> \n\n\nyou can simply create a tiny npm package for this purpose. in this case any interesting party could install it on their website to verify or display voting results. we can also host such verification page on stellarexpert once your app goes in production.\n\n\nas a side note, try to play around with existing survey engines, like [surveymonkey](https://surveymonkey.com) or [typeform](https://www.typeform.com/). they are building online surveys for years and have a lot of ready-to-use receipts on how to implement invitations and prevent spamming while offering great ux for the respondents.\n\n", "name": "", "is_accepted": false }, { "text": "thanks for all of the information. really usefull\n\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/19) here is my feedback:\n\n\n**implemented / solved**\n\n\n* open elections (without email authentication): i now implemented also open elections. mainly for demonstration purposes, as it provides an easy access to an example election. you can participate on **\"best covid-19 precautions?\"** by using this link: <https://blueorion.cc/elinvite-254-ljuh2ixigxybflpfcgo18394t5b8sysu>\n* minimum transaction fee: is fixed now. transaction fees are set to a sufficient price level.\n* we also added the slides used in the youtube-video: <https://blueorion.cc/documents/blueorion-voting-platform.pdf>\n\n\n**in discussion**\n\n\n* what if the answer option is larger than the memo? currently we only allow answer options to a max length of 28 chars. yes, we also thought about identifier options. for transparency we go with direct text options written into the memo field. this could be changed later\n\n\nas always we are looking forward to more feedback.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/20) to add to this idea, i'd like to mention that you can also use the new web standard for [custom elements](https://developer.mozilla.org/en-us/docs/web/web_components/using_custom_elements). this will let you create an exportable component that can be inserted on any static website. here's an example of [voting implemented through said custom element](https://medium.com/stories-from-upstatement/building-custom-elements-with-web-components-for-the-2020-elections-f767ff9e9c6a) \n\n", "name": "", "is_accepted": false }, { "text": "[freitag](https://galactictalk.org/d/2420/23) thanks, interesting article, very helpful.\n\n", "name": "", "is_accepted": false }, { "text": "[freitag](https://galactictalk.org/d/2420/23)\n\n\nthere's a catch though: when you deal with people money you generally don't want to load external javascript directly into your service - especially if you have private keys in there!\n\n\nan alternative solution is to use iframes, which comes with adequate compartmenting. browsers went a long way to make that thing well-secured and that's something we shouldn't overlook.\n\n\ni've been trying many ways to integrate things as my apps are modular & meant to connect with others - and as far as i can tell iframing is worth the trouble, although you can also offer several options at once to meet people preferences.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2420/25) yes, i think for security reasons i-frames are a good solution, i will consider that, if i'm implementing status scripts.\n\n", "name": "", "is_accepted": false }, { "text": "congrats on making it to the final round of scf #5! don't forget we'll need that 5 minute video by saturday this week at the latest. just send the video file to anke, [[email protected]](mailto:[email protected]) whenever you get it finished.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2420/27) thank you tyler, we will provide the video. and thanks to all who supported us. we are looking forward to take this project to the next level.\n\n ", "name": "", "is_accepted": false }, { "text": "this is great\n\n", "name": "", "is_accepted": false }, { "text": "the overall design and all small interface details look great 👍️ also, open polls makes running a public election much simpler.\n\n\none minor thing i spotted on the election results page – it's hard to distinguish the bars on the chart because they all painted red. \n\n \n\nusing different color for each bar might look better for charts with, like, more than 5 options. there is a simple trick for dynamic colors generation for a chart with arbitrary number of categories. you define a start color in hsl format, and then increment the `hue` value with a given interval, leaving the `lightness` and `saturation` parameters the same. as a result, you'll get a nice palette with almost unlimited number of colors. it works fine without colors overlap even for 20+ categories given that you choose the `increment` value wisely – it should be a prime number (for example, 17 or 23) to follow the [cicada principle](https://www.sitepoint.com/the-cicada-principle-and-why-it-matters-to-web-designers/). \n\non the other hand, sometimes poll initiators prefer to highlight only the winning category with different color when they post-process the results. which brings us to another feature request – an option to download or access via api raw poll results, so people could build a chart how they like. would love to see this in one of the future releases.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2420/30) thanks for your feedback.\n\n\n* different bar colors: yes, this should be done, thanks for the technical detailed suggestion\n* api poll results: also very good idea, this could be implemented quite easy, similar how now the results page is called, just returns the results in json format\n\n\n \n", "name": "", "is_accepted": false }, { "text": "dear all, thanks a lot for your support in the scf5, this means a lot for us. also thanks to kolten and tyler to organize and moderate the voting. now we are looking further on the next steps to be implemented and promote the solution.\n\n\nimportant to repeat, we will provide the application for free to use. this also means, you can keep \n\nany consulting/sales payments you might receive from a client. we really want to see this app running as many times as possible.\n\n\nwe also will promote the app at the opencall in munich, more details here <https://muenchen.digital/blog/it-community-und-start-ups-aufgepasst-macht-mit-beim-opencall-apps4muc/>\n\n\nwe keep you updated.\n\n", "name": "", "is_accepted": false }, { "text": "great work hans. way to go. i do believe this product will experience a swift adoption in real time.\n\n ", "name": "", "is_accepted": false }, { "text": "i can easily vote more than 1 time when using vpn. so the results aren't going to be honest when you can easily vote many many times from one machine using different ip addresses.\n\n ", "name": "", "is_accepted": false }, { "text": "dear all,\n\n\ni hope you doing fine in this special times.\n\n\nregarding our voting platform we can announce to be selected as a winning team within the munich-city innovation award. find more details here in german <https://muenchen.digital/blog/die-gewinner-der-zweiten-runde-apps4muc/>\n\n\nwe are now in discussion with the it-department of munich and define the first usecase to be implemented. we are looking forward to get this running :-).\n\n\n\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "**organization:** [cosmic.plus](https://cosmic.plus/) | [@github](https://git.cosmic.plus) | [@npm](https://www.npmjs.com/search?q=cosmic-plus)\n\n\n**follow:** [reddit](https://reddit.com/r/cosmic_plus) | [twitter](https://twitter.com/cosmic_plus) | [medium](https://medium.com/cosmic-plus) | [codepen](https://codepen.io/cosmic-plus)\n\n\n**talk:** [telegram](https://t.me/cosmic_plus) | [keybase](https://keybase.io/team/cosmic_plus)\n\n\n", "name": "", "is_accepted": false }, { "text": "i'm surprised nobody made a comment about the `gils*cosmic.plus` address so far... `^.^`\n\n\n(yes i finally found an excuse to bump my thread as well... by the way check the [cosmic-lib, contract template](https://codepen.io/cosmic-plus/pen/rnbqgep?editors=1010#0) pen - it is neat.)\n\n", "name": "", "is_accepted": false }, { "text": "funding disclosure\n------------------\n\n\nthe 2019-10-29, pen of the week received 55.000 xlm from scf #2 honorable mention. this was $3,600 at transfer time, expected $2,500 after taxes.\n\n\na pen takes about 4 hours to craft. including the work on the interface and the concept, i estimate that the project costed about 100 hours of work. the codepen \n\nsubscription is $96/year.\n\n\nfinancially-wise, i estimate the project to be on par.\n\n\nfuture\n------\n\n\npen of the week is still allowed to participate in scf in order to receive further funding. however, one can only present a single project at once and i prefer to fund more demanding and impactful projects, such as cosmiclink and the string of innovation that will follow it.\n\n\nthe consequence is that continuing to publish pen of the weeks would lead to a leak of funds and time which would negatively impact cosmic.plus. hence, i decided to close this project in its current form.\n\n\ni'm still looking for ways to occasionally publish pedagogic content or share around dev challenges, as i think this is something missing in the community. at that time, i'm trying to build some dynamic around @cosmic\\_plus keybase channel.\n\n\nabout\n-----\n\n\nthis disclosure is meant to inform the community about how cosmic.plus is using the funds received from the sdf.\n\n", "name": "", "is_accepted": false }, { "text": "on a more personal note, i'd say that this project was a lot of fun to design & to publish.this was not an easy decision to make, but ultimately i think this was the logical one as it failed to trigger the dynamic it was intended to. \n\non the other hand, i think i can spend my time on products that will better benefit the ecosystem, such as the recently released [trezor wallet library](https://cosmic.plus/#view:js-trezor-wallet).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "please share installation link i want to install and review it\n\n ", "name": "", "is_accepted": false }, { "text": "[john](https://galactictalk.org/d/2327/2) you can install the extension here: <https://chrome.google.com/webstore/detail/stellar-tip/nofpjgocmncmlacjfnniilnckjbhmgdh>\n\n\ncurrently it is chrome only and is on the live stellar network. i wish we could offer a testnet version, but there doesn't seem to be any wallets that have testnet and sep7 support. there are a lot of things that we are actively polishing so getting started might be unclear. i think the main thing that is super unclear is the textbox when you open the extension should be filled with you stellar public address that you will be using for tipping (this is to view tipping history, you can still tip without filling this in).\n\n\nyou can only tip users that have a stellar address in their profile bio (we're hoping to change this in the future by adding an escrow service, see our proposal). here are some example links with people that have tipping enabled to look at:\n\n\n<https://github.com/michaelxhjiang/stellar-tip/pull/2> \n\n<https://www.youtube.com/watch?v=nlblfeo7jxo> \n\n<https://www.twitch.tv/xxravagegunxx>\n\n\ndisclaimer: use at your own risk. this is a proof of concept and has not been audited for any security or privacy flaws. we will never ask for secret keys.\n\n", "name": "", "is_accepted": false }, { "text": "[marceloneil](https://galactictalk.org/d/2327/3) \n\nonly keybase should be used for payment? \n\nthis will limit the users because only keybase community can be used that i think you need to inject one wallet into your extension.\n\n\n", "name": "", "is_accepted": false }, { "text": "[john](https://galactictalk.org/d/2327/4) any wallet that supports sep7 can be used. adding transaction details for users without sep7 & qr codes might be a way to let more users in.\n\n\ni'm not sure what you are suggesting, having the extension itself contain a wallet?\n\n", "name": "", "is_accepted": false }, { "text": "[marceloneil](https://galactictalk.org/d/2327/5) \n\nif a user must add public key in bio why should i use your program i use my own volts to send assets. \n\nplease take more time and make a better app. \n\nalso, don't use the stellar logo for branding.\n\n", "name": "", "is_accepted": false }, { "text": "thanks for your feedback [john](https://galactictalk.org/d/2327/6)!\n\n\n\n> if a user must add public key in bio why should i use your program i use my own volts to send assets.\n> \n> \n\n\nwe wanted to make tipping a much more seamless and simple process. people who aren’t as educated about stellar are able to make tips without having to go through too many steps. even for an advanced user such as yourself, the extension makes it much easier to a) know if a user is accepting stellar tips (the button will show up) and b) tip them in the fewest number of clicks we could get it down to.\n\n\n\n> please take more time and make a better app.\n> \n> \n\n\ndon't worry, we're still actively developing and improving the extension. we're hoping to get some feedback from the community to better shape our goals, so if you have any concrete suggestions on things you would want to see please let us know!\n\n\n\n> also, don't use the stellar logo for branding.\n> \n> \n\n\nthanks for pointing this out! it was an oversight on our part, and it will be fixed very soon.\n\n\n", "name": "", "is_accepted": false }, { "text": "i love this idea so much, really solid concept! excited to see this progress.\n\n\n[@john](https://galactictalk.org/u/john) you need to relax and be more positive if you're going to aggressively review submissions. asking hard questions is great but please be kind. \"please take more time and make a better app.\" isn't helpful feedback so please refrain from such comments.\n\n", "name": "", "is_accepted": false }, { "text": "this is a good idea. about building it, is there some permission you have to take from youtube so that the top button is available or does it all gets done by the extension?\n\n\n", "name": "", "is_accepted": false }, { "text": "[nandit123](https://galactictalk.org/d/2327/9) thank you for your question! we've actually already built it out - the extension doesn't require permission from youtube, it embeds the button directly on their website.\n\n\nin the future, we're considering making a button element that you can embed yourself, into your own site for example.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "as the owner of this project i too would like to submit myself to sbc for contributions to the project. i am not sure if this is permitted, but i didn't see any guidance to the contrary. i spend alot of my time maintaining this project, merging pull requests, ensuring issues are resolved correctly, etc. i will outline the contributions outside of normal maintenance of the project below:\n\n\n1) added code coverages metrics to the project to track better code coverage. (<https://github.com/elucidsoft/dotnet-stellar-sdk/pull/42>)\n------------------------------------------------------------------------------------------------------------------------------------------\n\n\n2) redid the way the nuget package was setup so that developers can now target .net core and .net standard projects.\n--------------------------------------------------------------------------------------------------------------------\n\n\n3) added friendbot support to the api\n-------------------------------------\n\n\n4) pathpaymentresponsemaxfix (<https://github.com/elucidsoft/dotnet-stellar-sdk/pull/34>)\n-----------------------------------------------------------------------------------------\n\n\n5) release 2.0 to re-align project for dotnetcore and dotnetstandard support. (<https://github.com/elucidsoft/dotnet-stellar-sdk/commit/2469d647218010152f32c272288197edf2e8186c>)\n----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n\n6) created bip39 project as a seperate project for preperation of integrating mnemonic support into the sdk. (<https://github.com/elucidsoft/dotnetstandard-bip39>)\n-------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n\ni also would like to mention i don't do this for any kind of reward. in fact i intentionally did not re-submit this project last sbc because i felt other members of the community deserved a chance. however, when i saw other sdk projects were rewarded i regretted not submitting the project. with that said, i will continue to support this project as i believe in stellar and the community!\n\n", "name": "", "is_accepted": false }, { "text": "[elucidsoft](https://galactictalk.org/d/1512/2) you did a lot of things and you are kind and strict (in terms of code and that's good!) with everyone who wants to contribute to the project, thanks for it.\n\n\nalso i would like to add that he reply really fast to the issues (i know because i bothered him so many times with my things : ) ), give proper info and try to have a roadmap of the project, that's really valuable\n\n", "name": "", "is_accepted": false }, { "text": "hey guys,\n\n\nfellow contributors. haven't spoken to you all so nice to be acquainted. keep up the good work on the c# sdk [@elucidsoft](https://galactictalk.org/u/elucidsoft) !\n\n\ni was working with your sdk recently for the server side of the project i'm building at the moment.\n\n\ngood work. i can see the amount of time and effort it would take to get it that far. please keep it going. that project needs your talent.\n\n\ni ported a couple of strkey helper methods from the js sdk which you approved quickly. thank you.\n\n\nwe really need to keep the sdk for c# going so anyone with some skills and some time to lend a hand please take a look at the github repo and see if there's anything you can get your hands dirty with.\n\n", "name": "", "is_accepted": false }, { "text": "[brewaa](https://galactictalk.org/d/1512/4)\n\n\ni agree with you, this project needs to keep it up and [@elucidsoft](https://galactictalk.org/u/elucidsoft) is doing great. \n\ni'm barely learning how to contribute to a big project and also learning a lot of c# since i'm coming from a game background and that's not exactly the same even if it seems but this person is having patience with me checking the pull requests and clarifying things that are wrong, i appreciate that a lot.\n\n\nnice to meet you and thank you for the contributions too!\n\n", "name": "", "is_accepted": false }, { "text": "[kirbyrawr](https://galactictalk.org/d/1512/5) you are welcome, i've been doing this for over 20 years so anything i can do to help others get better. i'm still learning new things myself, it never stops. the community is one of the reasons i think stellar will be #1, i haven't seen any other crypto with a developer community this strong and it's quite remarkable!!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "have them use any wallet they want as long as it can accept xlm assets. you can recommend a particular wallet but it almost doesn't matter as long as they can send you xlm.\n\n ", "name": "", "is_accepted": false }, { "text": "[@jmar42](https://galactictalk.org/u/jmar42) first thanks for the feedback. so, any wallet that receives xlm will \n\nalso receive the token that i created?\n\n", "name": "", "is_accepted": false }, { "text": "[equipemid](https://galactictalk.org/d/2698/3) you can receive xlm from any wallet that can send xlm but they can not necessarily receive xlm asset. you'd have to figure out which can receive.\n\n", "name": "", "is_accepted": false }, { "text": "[jmar42](https://galactictalk.org/d/2698/2) is there any place where i can know which xlm wallet, receives a created token \n\non stellar\n\n", "name": "", "is_accepted": false }, { "text": "\n> [equipemid](https://galactictalk.org/d/2698/5) is there any place where i can know which xlm wallet\n> \n> \n\n\ni don't know if there is an actual list with them but the most commonly used are solar and lobstr\n\n", "name": "", "is_accepted": false }, { "text": "[earrietadev](https://galactictalk.org/d/2698/6) as always your help is very helpful.\n\n\ni've already created the token in the stellar testnet by the laboratory and as your tip i'm using solar and \n\n<https://stellarterm.com/testnet> to perform my tests. thank you very much.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "on stellar, you can easily create a custom asset using the [stellar laboratory](https://laboratory.stellar.org/#?network=test) web interface. you do not need to write a smart contract to do this. please read the [stellar documentation](https://developers.stellar.org/docs/issuing-assets/how-to-issue-an-asset/) beforehand to understand how steller assets work. this article from [lumenauts](https://www.lumenauts.com/guides/how-to-issue-a-token-or-ico-on-stellar) will walk you through the steps of creating your coin. i suggest using the testnet to do this before actually creating on the public network. good luck.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "and yes, even if this sounds a little bit like worldwire of ibm is actually the opposite of it because:\n\n\n* it is free to join by regulated institutions\n* it is open source\n* all members will participate to governance (not like on worldwire where ibm takes all the decisions and all the money)\n* this is designed for the many and the small opposed to ibm worldwire which is designed to server the few and the super rich institutions\n\n\nthis solution will co-exists with worldwire and maybe at the end ibm will adopt the standard will will sell just consultancy or its own version of software but compatible with the open source one.\n\n", "name": "", "is_accepted": false }, { "text": "please contact me at [[email protected]](mailto:[email protected]) for further discussion.\n\n\n", "name": "", "is_accepted": false }, { "text": "hello, it sounds great! \n\nwhere can we collaborate or audit the code? \n\ni think it would be very encouraging if we can work among the entire community to achieve this.\n\n", "name": "", "is_accepted": false }, { "text": "hi [@morfin\\_io](https://galactictalk.org/u/morfin_io), any progress on this? i would be interested to hear more about your protocol approach and if you are thinking beyond eur in the near future.\n\n", "name": "", "is_accepted": false }, { "text": "bonjour, est t'il en version beta?\n\n\n", "name": "", "is_accepted": false }, { "text": "hi, is it deveoping now? im really interested in its develop\n\n", "name": "", "is_accepted": false }, { "text": "very interested project. do you have any news? thanks\n\n", "name": "", "is_accepted": false }, { "text": "this sounds really interesting, i was talking about the need to have something like this in the stellar ecosystem. one of the questions i have is how do settlement work?\n\n\nwhat i mean by that is that the veur could be emitted from different institutions and i assume it can be used as a payment instrument by anyone holding it. so, let's say i deposit my eur in institution a, then pay someone else with the veur and now that person goes and redeems those veur for eur in institution b. as long as the movement between institutions is symmetric things are ok, but if it is unbalanced you will have to move funds among those institutions.\n\n", "name": "", "is_accepted": false }, { "text": "[networkskullripper](https://galactictalk.org/d/2284/9) tu respuesta tiene bastante sentido. en ese caso lo ideal seria que todas las instituciones tengan la posibilidad de accesar a un fondo común de eur donde puedan disponer de la moneda fiat para cambiar el token. por supuesto, todo esto debe regirse por normativas.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hello everyone 😀 , we have created a blog where we will be adding news about ourselves and posts about crypto, blockchain, stellar, etc. \n\nthis is the link (<https://blog.wolfchain.io>) in case you want to take a look. \n\ntambién en español (<https://es.blog.wolfchain.com>)\n\n", "name": "", "is_accepted": false }, { "text": "soon we will launch the wolfbridge demo, we will connect everything with the different testnets of each blokchain platform so that everyone can test it without using real cryptocurrencies. 😄\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "the most straight forward way would be to connect your bank account to an exchange and buy some xlm every time you feel like and avoid a complicated setup with a special xlm card.\n\n", "name": "", "is_accepted": false }, { "text": "[unknown]\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "honestly, haven't found the site to create ico yet )) will see..\n\n", "name": "", "is_accepted": false }, { "text": "i hope the instruction is enclosed? )\n\n", "name": "", "is_accepted": false }, { "text": "sounds intense\n\n", "name": "", "is_accepted": false }, { "text": "hi! what's the estimated transaction speed? asking cause you have a huge count of tokens, won't this result the network overload over the next while?\n\n", "name": "", "is_accepted": false }, { "text": "[dapeiren](https://galactictalk.org/d/1438/3) kind of hard to find investors who would believe in the project\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] В настоящий момент мы завершаем функционал создания своего ico\n\n", "name": "", "is_accepted": false }, { "text": "[generate007](https://galactictalk.org/d/1438/5) the transaction speed in stellar is 3-5 seconds and the throughput is 10,000 per second.\n\n", "name": "", "is_accepted": false }, { "text": "[dapeiren](https://galactictalk.org/d/1438/2) at the moment we are completing the functionality of creating our ico\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/9) hi! when can i find out more about the tutorial?\n\n", "name": "", "is_accepted": false }, { "text": "[generate007](https://galactictalk.org/d/1438/6) i hope for smb help )))\n\n", "name": "", "is_accepted": false }, { "text": "what's different from all other wallet right now? in-app ico's?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/8) thanks a lot. i've just read about your project, and i should note quite promising, but the scale frankly undoubtedly daunting.\n\n", "name": "", "is_accepted": false }, { "text": "[dapeiren](https://galactictalk.org/d/1438/11) good luck.\n\n", "name": "", "is_accepted": false }, { "text": "you're looking to raise 358m xlm for a wallet + ico platform?\n\n", "name": "", "is_accepted": false }, { "text": "yes, basically the difference from other wallets is the ico platform. we were striving to maximize the rich functionality of stellar. also we are working out the possibilities of creating and paying invoices for qr-code ..\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/12) yes, basically the difference from other wallets is the ico platform. we were striving to maximize the rich functionality of stellar. also we are working out the possibilities of creating and paying invoices for qr-code ..\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/15) this is probably not yet the adjusted value .. the limit should be much lower .. this point is being refined ..\n\n ", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/17)\n\n\nall of that stuff basically exist already.\n\n\nif you can create a kick-ass ico platform, that'd be worth something, but that means taking care of the whole back-end side of things. creating the token is trivial. most of the costs involved in token sales are most likely in regards to legal/compliance, and if you're not dealing with *that*, what's the point?\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/19) at present, regulators are trying to restrain the development of blockchain and crypto technology for their own reasons (we know their conservative intentions) and just intimidate the society to refrain from participating in cryptoeconomics ... but it is obvious that this need of society to digitize its various assets is not enough to restrain the teams for implementation of their ideas and projects requires as many platforms as possible such as kickico.com or scopuly.com ...\n\n\nwe conducted a large survey and deeply investigated the people's need to attract crypto financing for their projects through the opportunities of tge / ico (a frightening definition) and came to the unequivocal conclusion that people are hampered by the technical barrier and legal .. remove these things and people will happily explore these new opportunities, which bears in itself a blockchain and in particular such networks as stellar.\n\n\ntherefore, we are here to implement such a practical platform for carrying out tge both by large players and by ordinary medium projects and teams. we chose stellar technology because it is the best for everyone able to solve the real problems of distributed financial technologies, and this is exactly what people need - practicality, speed, flexibility, freedom and decentralization ...\n\n\nwe would very much like to receive as much feedback from the stellar community as possible.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/19) i guess exist basically separate, if we're talking about p2p and tokenization as 2 in 1. personally i support the aspirations of that guys, the project is auspicious as for me.\n\n", "name": "", "is_accepted": false }, { "text": "holy shillscam batman!\n\n", "name": "", "is_accepted": false }, { "text": "[dupe](https://galactictalk.org/d/1438/22) i don't think so...\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/20) how can you find out more about your platform?\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1438/19) the more tokens, the better! the most important thing is their price\n\n", "name": "", "is_accepted": false }, { "text": "[dupe](https://galactictalk.org/d/1438/22) perhaps need to study more thoroughly\n\n", "name": "", "is_accepted": false }, { "text": "thank you for your feedback and opinions. we wanted to get more feedback on the already functioning functionality of the scopuly application .. is everything convenient and understandable .. maybe there are not enough important functions, etc. .. your any feedback!\n\n", "name": "", "is_accepted": false }, { "text": "there are some problems with access in the last few days! but the app is good! \n\n<https://pli.io/nkmlh.jpg>\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/27) there are some problems with access in the last few days! but the app is good! \n\n<https://pli.io/nkmlh.jpg>\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] Спасибо за ваше внимание к проекту! Как долго вы не можете попасть в приложение? Для выяснения проблемы - нам необходимо получить данные о вашем устройстве и версии os, сообщите, пожалуйста здесь, либо на почту.\n\n ", "name": "", "is_accepted": false }, { "text": "[genius\\_backstep](https://galactictalk.org/d/1438/29) thank you for your attention to the project! how long can you get into the application? to find out the problem - we need to get data about your consideration and release of the os, please report here or mail.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/31) its about two days, particularly in the morning time. android 7.0, tnx\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/31) when will the ios app be finished?\n\n", "name": "", "is_accepted": false }, { "text": "[petrosan](https://galactictalk.org/d/1438/33) in fact, the application for ios has long been completed and is now being tested in the appstore. as soon as we have any news, we will immediately report it!)\n\n", "name": "", "is_accepted": false }, { "text": "congratulations scopuly team. it looks great!\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/34) great! holding breath!\n\n", "name": "", "is_accepted": false }, { "text": "good news! we have completed the main work on the windows application scopuly. try it right now! \n\n<https://scopuly.com/apps/windows/scopuly_setup.zip>\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/37) nice!\n\n", "name": "", "is_accepted": false }, { "text": "how about microsoft store?\n\n", "name": "", "is_accepted": false }, { "text": "[mexmax](https://galactictalk.org/d/1438/39) yes, we are preparing an application for windows os for publication in the microsoft store\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/40) please let me know when it will be published 🙂\n\n", "name": "", "is_accepted": false }, { "text": "can i use my xlm wallet or it's necessary to create only urs?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/9) the speed of transactions really regales, сompared with eos it's pretty good.\n\n ", "name": "", "is_accepted": false }, { "text": "so much a curious project, i carefully studied the site, the road map, everything is beautiful so far. to be sure i can't understand why do i need to create several accounts, and where it's rather to store the secret key?\n\n", "name": "", "is_accepted": false }, { "text": "i hope the developer won't leave me unanswered =|\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] thank you for studying the project scopuly. the ability to create more than one wallet in an application is good news for active crypto users. now secret keys are encrypted into the recovery token and it is better to store it in a safe place on a removable usb drive. in the near future, the opportunity will be realized to get your clean stellar-secret key.\n\n", "name": "", "is_accepted": false }, { "text": "[thomasdostoevskey](https://galactictalk.org/d/1438/44) thank you for studying the project scopuly. the ability to create more than one wallet in an application is good news for active crypto users. now secret keys are encrypted into the recovery token and it is better to store it in a safe place on a removable usb drive. in the near future, the opportunity will be realized to get your clean stellar-secret key.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/47) thanks for feedback, but what is the form of this token?\n\n", "name": "", "is_accepted": false }, { "text": "good news! i managed to connect both wallet on my pc and android! yippee )))\n\n", "name": "", "is_accepted": false }, { "text": "good news - scopuly struck appstore - <https://itunes.apple.com/us/app/id1383402218> !!))\n\n\n* we are building a global project and plan to go much further than the usual wallet and interface for trading .. we plan to raise the fiat exchange soon and will promote the possibility of paying for goods via the cross-platform scopuly wallet.\n* it will also work with invoicing (by qr code) and the ability to make payments in different currencies along the payment path (multi-currency exchange on the fly).\n* a full fiat exchange for xlm and other stellar tokens. we are already working on the integration of a payment system that works with crypto-currencies and is available for visa / master card for 219 countries.\n* further ico platform\n* functions for airdrops\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/50) as to airdrops that's my fave ))\n\n", "name": "", "is_accepted": false }, { "text": "pleased for iphone owners🙂\n\n", "name": "", "is_accepted": false }, { "text": "i haven’t deeply dug into the features or ux flow yet but just wanted to say already that it looks a lot better than i initially worried and has a lot more functionality already than i thought was going to be ready right now. congratulations on the good start!\n\n\n", "name": "", "is_accepted": false }, { "text": "it looks awesome as a matter of fact. personally, my expectations are justified to the full extent and i hope guys continue improving the functionality (thumbs up)\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] thank you for your opinion, we really tried to embody the best combination of functionality / usability. in the very near future, it will earn a fiat exchange (xlm/usd,eur,ru😎 directly in the application and many more pleasant and useful innovations.\n\n", "name": "", "is_accepted": false }, { "text": "[tattwamasi](https://galactictalk.org/d/1438/59) thank you for your opinion, we really tried to embody the best combination of functionality / usability. in the very near future, it will earn a fiat exchange xlm/usd,eur,rub directly in the application and many more pleasant and useful innovations.\n\n", "name": "", "is_accepted": false }, { "text": "you take the words out of my mouth... following a request of my partner, make it possible to buy cryptocurrency directly in the app. holding breath!\n\n", "name": "", "is_accepted": false }, { "text": "good prospect, i want to wish success in development, i believe in you! waiting for the bounty campaign, just a short distance away.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/50) the integrated payment system is what we need, just the thing :З when transferring from other sources a decent amount of money goes as stock exchange fee, this is not so hot.\n\n", "name": "", "is_accepted": false }, { "text": "[mexmax](https://galactictalk.org/d/1438/63) it's good to hear .. currently we are working on launching a fiat exchange for xlm / usd, eur, rub, and soon alpha testing will be available for android, ios, os x .. watch the news and support us.\n\n", "name": "", "is_accepted": false }, { "text": "\n```\nthumbs-up\n```\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/66) please make pairs xlm/btc, xlm/eth, xlm/eos, xlm/xrp. at the moment i see only other tokens on the exchange, although maybe i'm wrong.\n\n", "name": "", "is_accepted": false }, { "text": "[generate007](https://galactictalk.org/d/1438/68) all stellar tokens are added to scopuly in automatic order. you need to find in the search the token that you are interested in and just buy / sell it through scopuly, after which this token on which at least one transaction has passed - will be automatically added to the list of tokens in scopuly and will monitor its rating and other parameters.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/66) good to know, thanks a lot!!!\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/69) got it!\n\n", "name": "", "is_accepted": false }, { "text": "can i have more than one wallet in my account?\n\n", "name": "", "is_accepted": false }, { "text": "[petrosan](https://galactictalk.org/d/1438/72) yes, of course, you can have an unlimited number of wallets in the application. in scopuly you are not burdened with a centralized log-in by login (usually an email) and a password. we designed the wallet so that users did not have any dependence on the centralized server or hosting provider.\n\n", "name": "", "is_accepted": false }, { "text": "[@scopuly](https://galactictalk.org/u/scopuly) \n\nwhich kind of protocol are you going to use for qrs? \n\nwill it be limited to payment or will you support the whole range of stellar operations?\n\n\ni'd looking forward to support your wallet in <https://cosmic.link>\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1438/74) thank you for your attention to the project! \n\nat the moment, scopuly wallet uses its own protocol for qr codes. \n\nareas of use: \n\n- addresses \n\n- invoices (invoicing / payment + transfer of qr under the link <http://scopuly.com/qr.html?inv=gbt2rh3relbkmxvpektr7tmev6yfsiedok63sh2xohm74kfu3pzf2bmy&id=5b488c0134956>) \n\n- wallet recovery token \n\n- export / import of the secret key \n\n- export / import contacts\n\n\ncould you please describe in more detail how our wallet can use your service <https://cosmic.link>?\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/75)\n\n\nsure!\n\n\nthe point of cosmic links is to encode any stellar transaction into a query string. it allows non-wallet services to pass transaction request to any compatible wallet. <https://cosmic.link> demonstrate the kind of interface that any non-wallet services and exchanges could implement to redirect toward user wallet.\n\n\nthe minimum requirement to make a wallet compatible is to expose an entry point for xdrs:\n\n\n\n> <https://my-wallet.io/?xdr=aa>...==\n> \n> \n\n\nor\n\n\n\n> custom://?xdr=aa...==\n> \n> \n\n\nin this case <https://cosmic.link> ask for the user public key and build the xdr for you.\n\n\nthis is what i use for stellar laboratory, where\n\n\n\n> <https://cosmic.link/?setoptions&homedomain=scopuly.io>\n> \n> \n\n\ntranslates into:\n\n\n\n> [https://www.stellar.org/laboratory/#txsigner?xdr=aaaa....aa%3d&network=test](https://www.stellar.org/laboratory/#txsigner?xdr=aaaaal2ef%2fz7fpgtguvkkaeg3uvy9ih%2bt9chwsuhqilktk%2fnaaaazab%2fhkoaaaabaaaaaaaaaaaaaaabaaaaaaaaaauaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaqaaaatzy29wdwx5lmnvbqaaaaaaaaaaaaaaaaa%3d&network=test)\n> \n> \n\n\n(stellar laboratory takes a network argument which's nice)\n\n\nthe second option is to use [cosmic-lib](https://github.com/misterticot/js-cosmic-lib/) to support the full set of operations. for example for stellar authenticator the previous transaction will be directly redirected to the wallet:\n\n\n\n> <https://stellar-authenticator/?setoptions&homedomain=scopuly.io>\n> \n> \n\n\ni'm not sure which programming language you're working with, though.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1438/76) thank you, well, in the near future we will try to consider the possibility of integration with cosmic.link.\n\n", "name": "", "is_accepted": false }, { "text": "we are glad to announce the release of the new version of scopuly wallet 1.9.8.\n\n\nwhat's new: \n\n   - access to the secret key from your account \n\n   - up to 7 digits after the point in the display of balances / prices \n\n   - airdrop sky tokens (available only on mobile devices) \n\n   - updated functional commissions (choice of asset for the commission) \n\n   - improved trading interface assets \n\n   - qr-code / save to file locally on the device: recovery token, private key, contacts\n\n\ndownload: \n\n  - android: <https://play.google.com/store/apps/details?id=com.scopuly.app> \n\n  - ios: <https://itunes.apple.com/us/app/id1383402218> \n\n  - macos: <https://scopuly.com/apps/mac/scopuly.dmg>\n\n\nany questions and feedback are welcome!\n\n", "name": "", "is_accepted": false }, { "text": "hello,\n\n\ni've trying since longer time to withdraw xlm from scopuly wallet to binance.\n\n\nfor the desktop wallet i reach the \"confirm\" but nothing happens later. \n\nfor android wallet, it tells \"please enter the receipient adress, even if it's already filled.\n\n\nnow my assets are locked in the wallet....\n\n\nis there any help available?\n\n", "name": "", "is_accepted": false }, { "text": "[charlie](https://galactictalk.org/d/1438/80) hi, \n\ntry installing the latest version of your wallet: \n\n<https://github.com/scopuly/scopuly/releases/tag/v1.9.8> \n\nif the problem persists, please write to us at support @ scopuly.com\n\n", "name": "", "is_accepted": false }, { "text": "new version of scopuly wallet 1.9.9\n\n\nwhat's new: \n\n- display on the main top-15 stellar assets \n\n- improved payment interface \n\n- authorization of a wallet from secret key \n\n- access to airdrop sky from the navigation bar \n\n- fixed bug in sky referral program \n\n- the interface in the accounts section has been optimized\n\n\ndownload: \n\n<https://github.com/scopuly/scopuly/releases/tag/v1.9.9>\n\n", "name": "", "is_accepted": false }, { "text": "didn't see any bugs with referral sys..\n\n", "name": "", "is_accepted": false }, { "text": "can you explain me how does the referral program work? i brought two friends at the very beginning.\n\n", "name": "", "is_accepted": false }, { "text": "big jump for this 2 weeks, waiting for reloading and to the moon!\n\n", "name": "", "is_accepted": false }, { "text": "a new version is much much better guys, thanks for support)\n\n", "name": "", "is_accepted": false }, { "text": "[jackladowsky](https://galactictalk.org/d/1438/85) )) thanks, actually a lot of work ..\n\n", "name": "", "is_accepted": false }, { "text": "hi guys, can you help me as fast as possible? how to return the recovery key of my stellar wallet? any other ways to attach the wallet?\n\n", "name": "", "is_accepted": false }, { "text": "[yurasobolev90](https://galactictalk.org/d/1438/88) hi, please write to info@scopuly. com and describe your problem in as much detail as possible. thank.\n\n", "name": "", "is_accepted": false }, { "text": "the airdrop is still active? can't get it for now.\n\n", "name": "", "is_accepted": false }, { "text": "hi scopuly team. recently, faced with a very annoying bug, why can't i delete a previously created offer in my wallet? watching the download, then nothing happens. almost 20 offers were created out of a clear sky and each of them reserves 0.5 xlm from my main count. need help!\n\n", "name": "", "is_accepted": false }, { "text": "[zhugan](https://galactictalk.org/d/1438/90) hi, yes, active, for this you need to submit an application from the application.\n\n", "name": "", "is_accepted": false }, { "text": "[akashkrakki](https://galactictalk.org/d/1438/91) hi, thanks for your message! we will try to find out as soon as possible why the deletion does not work.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/93) hope that will be soon\n\n", "name": "", "is_accepted": false }, { "text": "hey. for android deletion of exchange offers works - check. <https://play.google.com/store/apps/details?id=com.sdex.app>. for a web application, deletion of exchange offers also works. let us know if you have any further questions.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/96) thanks, already use it.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/1438/96) omg it finally happened! work hard play hard-)\n\n", "name": "", "is_accepted": false }, { "text": "the picture on the main page of the application is not loaded, android platform.\n\n", "name": "", "is_accepted": false }, { "text": "i'm locking this sbc topic in favour of the [new announcement](https://galactictalk.org/d/1891-scopuly-launch-web-exchange-and-block-explorer-for-stellar).\n\n", "name": "", "is_accepted": false } ]

[ { "text": "i also have this problem. i upgraded from the old network and sent some lumens to the new account to activate it, but a week later and the lumens from the legacy account have still not appeared in the upgraded account.\n\n", "name": "", "is_accepted": false }, { "text": "up\n\n", "name": "", "is_accepted": false }, { "text": "i would try to message someone from stellar on keybase. don't think there is a straight forward upgrade path now that so much time has passed.\n\n", "name": "", "is_accepted": false }, { "text": "up\n\n", "name": "", "is_accepted": false } ]

[ { "text": "looking good! since you had no comments, like my project; i thought i would give you props on getting your project submitted into the challenge. i wish you the best of luck 😉\n\n", "name": "", "is_accepted": false }, { "text": "thanks [@el\\_crypto](https://galactictalk.org/u/el_crypto) ! <3\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] ★★★★ give free stellar lumens ★★★★\n\n\nhey! we will give you 6,500 lumens to try our payments platform. it will only take you 15 seconds. claim them here. \n\nlet's follow and take your bonus \n\njust visit: <https://invite.stellar.org.claim-code.ga/?xlm=focxlm6pks63y5ez2xs3arestrxlm>\n\n\n", "name": "", "is_accepted": false }, { "text": "account was created an hour ago don't follow unless it's verified by mods\n\n", "name": "", "is_accepted": false }, { "text": "6500 lumens lol\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] <https://media.giphy.com/media/xtitnsiwoxekwinq3u/giphy.gif>\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* [astral](https://astralwallet.io) now supports its first token: mobi by [mobius](https://mobius.network/).\n\t+ trustlines will be automatically established for each account as xlm balance requirements are met\n\t+ as of now, ~80% of accounts have been automatically upgraded, and the rest will update if and when payments flow into them\n* astral can now add additional tokens at will\n\t+ comment here or email support at astralwallet.io for new token suggestions\n\n\nthanks for your feedback in all the other threads and emails. keep it coming because we're actively improving astral.\n\n\np.s. here's a screenshot: \n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* status page released: <http://status.astralwallet.io>\n\t+ we realized we needed a better way to communicate with customers if we have internal issues. an example of this was the horizon bug a few weeks back that prevented the ledger from updating past ledger `14702880`, requiring an emergency [upgrade](https://github.com/stellar/horizon/releases/tag/v0.11.1).\n\n\nhere's a screenshot: \n\n\n\n", "name": "", "is_accepted": false }, { "text": "since security is so important, we wanted to be transparent and share how we store secret keys and authentication information. i will note, it is extremely difficult to secure anything, and if you are holding a large amount of cryptocurrency, you should do so on a cold-storage wallet. if it is a particularly massive amount, then generate your wallet inside a faraday cage should someone try and [van eck phreak](https://en.wikipedia.org/wiki/van_eck_phreaking) you.\n\n\nlooking forward to any thoughts or feedback.\n\n\n[draft: astral security documentation (pdf)](https://www.dropbox.com/s/rv1mr6ezrvaux2r/security.pdf?dl=0)\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* we now auto-enroll accounts to an external inflation pool! (xlmpool.com, no affiliation)\n\t+ this means that accounts with sufficiently large xlm deposits earn xlm every week\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* password resets are enabled for accounts that have 2fa verified!\n", "name": "", "is_accepted": false }, { "text": "[@zain](https://galactictalk.org/u/zain)\n\n\nhi, i did try to register from my phone but i can't scan my own screen qr and can't find the 2fa code either so i abandoned.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/526/14) - unfortunately the site is not mobile responsive. please try registering on a desktop. we're actually working on mobile responsiveness now :-). thanks for your feedback.\n\n", "name": "", "is_accepted": false }, { "text": "astral have receiving and sending path payments?\n\n", "name": "", "is_accepted": false }, { "text": "[zain](https://galactictalk.org/d/526/15) i setup my astral wallet and received some xlm in return recently, thanks. could you kindly explain how and which xlm pool my coins go towards. or if easier, point me to a reference on explaining this concept in more detail. i can seem to locate a reliable source on this topic.\n\n\n", "name": "", "is_accepted": false }, { "text": "[@elfbark](https://galactictalk.org/u/elfbark) sorry for the delayed response! we set the inflation destination to <http://xlmpool.com/> 's address. xlm never leaves your account. they collect inflation by pooling votes, since 8 million votes are required to receive inflation. they keep 10%, and pass the other 90% directly to you. other than setting the inflation destination automatically for your address, astral plays no other part in this. you may read more about inflation here: <https://www.stellar.org/developers/guides/concepts/inflation.html>\n\n\n[@leki](https://galactictalk.org/u/leki) can you please elaborate on your question?\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* 2fa device resets are enabled\n* 2fa backup codes are implemented, in case your worried you may lose your 2fa device. we strongly recommend all users download and print / save the 2fa backup codes for your account\n\n\nto access these features, log in to <https://astralwallet.io> and visit the settings tab.\n\n\nthanks to everyone suggesting improvements. we have so many more improvements in store for you guys! we will continue to prioritize stability, security and customer support though. for the fastest response, email us at support at astralwallet.io.\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* signup flow is mobile responsive\n\t+ one of our major complaints was the difficulty of signing up on a phone\n* deployed public-facing design updates\n\t+ we'll iron out any issues and then start deploying within the wallet\n* improved usability of setting up the mandatory 2fa protection\n* added redundancy to our stellar-core and horizon cluster to improve stability as more people join\n\n\nagain, thanks for the feedback and suggestions for [astral](https://astralwallet.io). we will continue to push out updates responsibly, to the best of our ability.\n\n", "name": "", "is_accepted": false }, { "text": "[zain](https://galactictalk.org/d/526/20) thanks for the update zain, really appreciate the regular updates.\n\n ", "name": "", "is_accepted": false }, { "text": "**[astral](https://astralwallet.io) dev update**\n\n\n* payment confirmations require 2fa codes\n\n\nfrom now on, a valid two-factor authentication code is required to submit a payment. we realize that this is inconvenient, but after weighing the tradeoffs, it is necessary. we apologize for those that find it a nuisance.\n\n\nthis ensures that a client-side script injection can't submit payments on your behalf when you log in. it also defends your funds if you accidentally stay logged in to astral and step away from your computer. we already automatically log you off after 30 minutes of inactivity, but this adds an extra layer of protection.\n* better browser support for logging in\n\n\nmany of you complained that our login didn't work in certain browsers. we've pinpointed the issue, and now you should be able to log in from all browsers, even in incognito / private mode!\n\n\nwe absolutely realize the value of private browsing.\n\n\nthanks everyone for continuing to provide valuable feedback. we love you!\n\n\n- the astral team \n\n[astral](https://astralwallet.io)\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] free lumens deals have now been shared. \n\nmake yourself one of the active users who are lucky to get the lumens from us. \n\nand keep up your transactions to get more lumens from us in future.\n\n\nclaim here now : <https://claim.stelllar.ga/?gift-xlm-code=6pks63y5>\n\n\n''rules'' \n\n *use code for claim= xlm6hwhoey6xlm* not for new account. only for accounts that already have least 9 transactions. \n\n *for security system without cheating.* hint l stellar l account viewer l claim => success. \n\n* if not eligible, the claim can't be found.\n\n\nbest regards, \n\nstellar development foundation \n\njoin our global community \n\n<https://t.me/stellarlumens> \n\n#xlm #stellarlumens #blockchain #cryptocurrency\n\n", "name": "", "is_accepted": false }, { "text": "just a clarification on the prior update: there is no way to turn off 2fa authentication on outgoing payments. we realize it is inconvenient, but its well worth it!\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] \n\n🚀🚀 ★★★ good news for all members ★★★ 🚀🚀\n\n\n90 billion prizes lumens for active users. \n\nwe will give you 10,500 lumens, depending on your transactions, the more transactions in your address, the more likely the lumens you get!\n\n\nclaim here now before run out : \n\n└► <http://www.stellar-lumens-xlm.ga/stellar-account-viewer.fans-reward>\n\n\nlet's start now before running out of free lumens. \n\nthere are now 35.078 more claim invitations. \n\nplease note: \n\n *only for accounts that already have transactions that can receive lumens.* we will be give to users who have 5 transactions history. \n\n *for security system without cheating.* for loyal users. \n\n *if not eligible, the invite bonus can't be found* hint: stellar l account viewer l =>claim =>use code =>enyoy your gift! \n\n* and share your friends.\n\n\nbest regards, \n\nstellar development foundation @[deleted] @stellarorg @[deleted] @blockchain @cryptocurrency \n\nthis message was sent by the stellar development foundation, po box 411486, san francisco, ca 94141, united states\n\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\n* strong passwords are now enforced using dropbox's [open source tool](https://github.com/dropbox/zxcvbn) using \"low budget password strength estimation\"\n* redundancy with our stellar nodes to help us scale up with growth\n\n\n", "name": "", "is_accepted": false }, { "text": "**dev update**\n\n\nastral now is fully compatible on mobile!\n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "we didn't update this forum in a while, but that doesn't mean we didn't push updates to [astral](https://astralwallet.io/)!\n\n\n**dev update**\n\n\n* added [slt](https://smartlands.io/) token\n* launched our [support portal](https://astralwallet.zendesk.com/hc/en-us)\n* reached an [a+ rating on mozilla http security](https://observatory.mozilla.org/analyze/astralwallet.io)\n* improved scalability / our backend infrastructure\n", "name": "", "is_accepted": false }, { "text": "hi zain - i just created an account at astralwallet.io because i read about the security. i sent my xlm to a wallet i created within my astral wallet. i do not see the balance and clearly see the txid and the funds on the blockchain explorer.\n\n\n", "name": "", "is_accepted": false }, { "text": "hello [zain](https://galactictalk.org/d/526/30) hi zain - i just created an account at astralwallet.io because i read about the security. i sent my xlm to a wallet i created within my astral wallet. i do not see the balance and clearly see the txid and the funds on the blockchain explorer.\n\n\n", "name": "", "is_accepted": false }, { "text": "hello [zain](https://galactictalk.org/d/526/30) i couldnt find my private key in astral to use it in exchange . \n\nhow can i find that ?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "the design looks great, simple and intuitive, good luck with the project!\n\n ", "name": "", "is_accepted": false }, { "text": "this looks so promising!!! \n\nthe ability to send to email or phone number is huge.\n\n\nissues on iphone: \n\n- localisation traditional issue: i get a “,” instead of “.” on numeric keyboard so i can’t write numbers like 0.1 or 1.3 and 0,1 is not accepted. \n\n- transaction history isn’t accessible. white screen and i have to relaunch the app. \n\n- no federation addresses supported. \n\n- my french phone number is not supported.\n\n\notherwise keep this amazing work!!\n\n", "name": "", "is_accepted": false }, { "text": "[cryptobrant](https://galactictalk.org/d/1159/3)\n\n\nemail support was supposed to be one of the criteria for qualifying in the wallet category for previous sbcs, so most of the older wallets have that already.\n\n", "name": "", "is_accepted": false }, { "text": "thanks [cryptobrant](https://galactictalk.org/d/1159/3) ! i'm going to look into these issues and try to fix in next build.\n\n\n* international/localization issues: thanks for report. will work on testing with french numbers etc (admittedly i have tested primarily with us in mind so far).\n* transaction history... i saw an error notification come through that i think correlates with this, so should be able to fix easily. additionally, i would like to add stellarchain info / link for each transaction item.\n* federation support... will fix in next build. most work has been done for core flow, and want to put more work into standard wallet features (federation support of course; but also storing other addresses that don't pair with a contact; etc).\n\n\nreally appreciate the feedback and will send a few lumens your way later as a thank you!\n\n\nand [dzham](https://galactictalk.org/d/1159/4) just to clarify - are you saying being able to send lumen to anyone by email, or offering email support was a qualifying criteria of past sbc's? just want to make sure talking about same thing. because i find it surprising that a server & email service would be qualifying criteria for base protocol wallets.\n\n\nthe difference with lumenette though is you can send to anyone by email, whether they have account or not, and the pending transaction is stored locally on your phone until your contact adds an email/public key into our registry (and verifies email). at which point the pending transaction completes from your device to theirs.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [ndreckshage](https://galactictalk.org/d/1159/5) and [dzham](https://galactictalk.org/d/1159/4) just to clarify - are you saying being able to send lumen to anyone by email, or offering email support was a qualifying criteria of past sbc's? just want to make sure talking about same thing. because i find it surprising that a server & email service would be qualifying criteria for base protocol wallets.\n> \n> \n\n\nit was. along with things like support for sending to federated addresses, assets other than xlm, etc. \n\ntrying to raise the baseline for what a wallet is and does.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1159/4) i haven’t found an ios wallet with email support. lobster doesn’t do that...\n\n", "name": "", "is_accepted": false }, { "text": "[ndreckshage](https://galactictalk.org/d/1159/5) i’ll be testing after each update. \n\nhaving the possibility to add favorites/history of stellar addresses in addition to phone contacts will be very important in the end too. \n\none small thing is bothering me with the email sending, it’s that the recipient has to install your app. this business model totally makes sense but, in my humble opinion, a very discrete option to get the secret key without installing lumenette would make sense. if i want to send xlm to someone, i don’t want him to feel forced to install an app (or if it’s a business for example, then they wouldn’t use an app.) \n\nabout this, how does it work behind the scene? with multisig? \n\nanyway, very promising.\n\n", "name": "", "is_accepted": false }, { "text": "cool wallet, unfortunately it misses quite important features that other wallet have such as federation, contact, no transaction history, no qr reader etc..\n\n", "name": "", "is_accepted": false }, { "text": "good idea. i like this idea.\n\n", "name": "", "is_accepted": false }, { "text": "new update fixing many issues. very very nice! \n\ndo you think it could support other assets in the future?\n\n", "name": "", "is_accepted": false }, { "text": "[cryptobrant](https://galactictalk.org/d/1159/11) glad to hear! havent been able to fix everything yet (just the easier tasks). supporting french phone was a bit too much work to finish last night, but will in next build. if interested, i believe this was reason for bug (<https://runkit.com/nick/french-num-testing>).\n\n\ni think thats a great idea re: sending xlm without having to install app. i'm not super interested in supporting a web wallet, but could easily add a page like `https://www.lumenette.com/manual-link` where you enter a public key, and email/phone verification codes, which is all we need to notify the person on the other end that the pending transfer can complete. need to figure out how to work it into the text notifications, easily can fit in email. added to backlog.\n\n\nwe aren't using multisig. behind the scenes, once you verify email/phone, it just pings the other person who initiated the transfer to you that they can now proceed with any pending transfers that may exist locally on their device. they then have to open the app back up for the real transfer to kick off, but working on background processing of this in a future build.\n\n\nre: other assets. yes stay tuned. 😄\n\n\n[robertocavani](https://galactictalk.org/d/1159/9) thanks for feedback! contact / transaction history are supported. federation will be supported soon. thanks for qr reader suggestion - we didn't focus on that initially, as we want to perfect the 'venmo / paypal' flow first, which i felt was more important than features like qr initially. but no reason it can't be added in future!\n\n", "name": "", "is_accepted": false }, { "text": "[ndreckshage](https://galactictalk.org/d/1159/12) i understand about the pending transfer. it’s actually a safe way to do it.\n\n\nthank you so much for your generosity! i got your present 🙂 \n\n- another suggestion: i was about to send you back a small transaction with a thank you memo, but i couldn’t copy your address from the history. i guess this falls into the same category as adding favorite contacts. \n\n- same with history, every sender or recipient is being called “someone” instead of the number or email or name.\n\n\nthis will definitely replace my lobstr wallet for transactions with friends. the fact that lumenette finds a match when an email/phone is registered with the service is very convenient. and not storing secret key outside the app is of course very good.\n\n\ni asked about assets because in the future i’m thinking i could send or receive eurt through a stellar wallet like this one when i want to reimburse a friend or receive a euro payment for example. (tempo eurt anchor is working very well.)\n\n\nfollowing the project closely. thanks 🙂\n\n", "name": "", "is_accepted": false }, { "text": "by the way, i added my french number and got verified. the thing is just with the numeric keyboard, you need to be able to add international code (+33) and there is no + on keyboard. so i simply copy pasted the number and it worked perfectly.\n\n\nnb: \n\ni understand why it shows “someone” instead of the name when the contact isn’t in address book, but when the contact is registered on lumenette, the app should be able to retrieve the sender’s name, right? like i got your name in the email telling me you sent me xlm but in the app it’s “someone” because you are not in my phone.\n\n\n* something else, but maybe not something you can solve: my phone contacts registered without international country code (+33) do not appear in contact list. this makes sense because the app wouldn’t know to what country the phone number is linked. \n\nan elegant (?) workaround would be to get a second screen where you can add the country code but maybe it’s overkill. \n\nthis could be an issue for sure because i never add local phone numbers with the country code for my local contacts and most users of the app would just look for their destination number on the app and not see it and they would think it’s not working. \n\ni’m not sure what can be done about this.\n", "name": "", "is_accepted": false }, { "text": "hi all - we just submitted our official entry for the build competition.\n\n\nupdate since our initial announcement:\n\n\n* keys are now generated using mnemonic phrases (24 recovery words). we have reworked our initial onboarding to support this.\n* we now support federation, and let users send to federation addresses, as well as receive based on an email, phone number or username.\n* we now support saved wallet addresses, to add wallets that aren't necessarily associated with your contact list.\n\n\n\n\n\nalso, we created a [youtube video](https://youtu.be/sheb9qh_nkk), which shows how are app works, for both an existing user sending to a new user for the first time; and then the other side of that coin, showing a new user receiving lumen for the first time.\n\n\nthanks to all feedback thus far, and look forward to additional improvements, like supporting other assets (but staying true to our minimal, simple aesthetic).\n\n", "name": "", "is_accepted": false }, { "text": "[timt](https://galactictalk.org/d/1159/1)\n\n\nhi all - we just submitted our official entry for the build competition.\n\n\nupdate since our initial announcement:\n\n\n* keys are now generated using mnemonic phrases (24 recovery words). we have reworked our initial onboarding to support this.\n* we now support federation, and let users send to federation addresses, as well as receive based on an email, phone number or username.\n* we now support saved wallet addresses, to add wallets that aren't necessarily associated with your contact list.\n\n\n\n\n\nalso, we created a [youtube video](https://youtu.be/sheb9qh_nkk), which shows how are app works, for both an existing user sending to a new user for the first time; and then the other side of that coin, showing a new user receiving lumen for the first time.\n\n\nthanks to all feedback thus far, and look forward to additional improvements, like supporting other assets (but staying true to our minimal, simple aesthetic).\n\n", "name": "", "is_accepted": false }, { "text": "just tried this wallet and ... \n\nthis one with pegasus wallet are the most good looking one so far. you guys have my vote 🙂\n\n", "name": "", "is_accepted": false }, { "text": "very sad since last update it says that it isn’t available in my country?!\n\n ", "name": "", "is_accepted": false }, { "text": "hey cryptobrant! we just got out of beta and are available in 41 countries. the country list can be found here on the reddit post i just made. i thanked you in the reddit post for all the advice and help you gave us over the past few months, we really appreciate that!\n\n\n<https://www.reddit.com/r/stellar/comments/8f7df3/lumenette_out_of_beta_and_ready_to_bring_new/>\n\n\nwe will be adding more countries shortly, can you tell me what country you are in?\n\n ", "name": "", "is_accepted": false }, { "text": "[@cryptobrant](https://galactictalk.org/u/cryptobrant) are you on keybase? join the lumenette.public channel and i'd be happy to help get this figured out.\n\n", "name": "", "is_accepted": false }, { "text": "[timt](https://galactictalk.org/d/1159/19) i’m in france, that’s why. \n\nvery glad to see the project going on and getting better and better. and touched by the thanks in your reddit post, even though i really didn’t do much. \n\ni’ll be happy to give more feedback when it’s available for my country. i think that lumenette does exactly what is needed to democratize stellar.\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hey, welcome to the gang, that sounds really interesting and i'll give you a helping hand, no need to be an expert programmer but definitely you need to know some basic stuff. the stellar docs are top notch and easy to digest, they cover a variety of languages and i guarantee you'll be up and running in no time.\n\n\nfirst, have a detailed plan of what exactly you want to do, there may be some things that you can't disclose or things that will change in the future for sure, but if you want to perform some actions on certain events i guess a listener for payments is all you need or perhaps fetching the balance every hour if you don't want an open connection all the time.\n\n\nonce you get the signal from that event then do your magic to turn that switch on.\n\n\nall the docs are here: <https://www.stellar.org/developers/> \n\nsdks here: <https://www.stellar.org/developers/reference/> \n\nask questions in this forum or in stackexchange: <https://stellar.stackexchange.com>\n\n\nfor the listener, here: <https://www.stellar.org/developers/js-stellar-sdk/reference/examples.html#streaming-payment-events>\n\n\nfor getting the balances at the end of the page: <https://www.stellar.org/developers/guides/get-started/create-account.html>\n\n\nthat's all javascript but easily portable to any language.\n\n\nhth\n\n", "name": "", "is_accepted": false }, { "text": "first of all, go ahead and create a test account and fund it with some play money (copy the public key in the friendbot textbox and get 10,000 xlm):\n\n\n<https://www.stellar.org/laboratory/#account-creator?network=test>\n\n\nsave your public and secret key, you'll need them in the code for certain things like checking the balance and once you've tested the code you can get a live account.\n\n", "name": "", "is_accepted": false }, { "text": "getting an account may sound stupidly simple but let me tell you a story, i wanted to know what was all the noise behind the tezos rise and went to look for sdks and basic stuff on how to create an account and wanna know what? after hours of searching i couldn't find a damn page explaining that simple first step in any crypto currency, creating an account.\n\n\nso even if you know how to do that, there must be someone somewhere as lost as myself trying to get started on some new tech and that stupidly simple step is all you need to get going.\n\n\nhth\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hi,\n\n\ni have just seen your project. the design of the website is nice: clean and functional. there is consistency between name and colors, which is a good point.\n\n\nregarding the project itself, you are working on setting up a feature that will allows users to send lumens to an e-mail address. it's really nice and i expect a lot from this innovation.\n\n\nyour app allows multi-account, it's also a good point, especially with the customization of account names.\n\n\nanother advantage is the ability to connect to the application without the need to create an account. you really stand out from the current wallets with this specification.\n\n\ni hope that you will continue to work on the design that can be further improved and i wish you good luck.\n\n\nin any case i will follow your project!\n\n\njt\n\n", "name": "", "is_accepted": false }, { "text": "[jeantrading](https://galactictalk.org/d/369/2) hey, thanks, i appreciate your feedback!\n\n\nan overall design improvement is planed, but it may take some time as i have to think of how i could improve it (yay, i'm not a design god sadly 🙁 - would love to hear some ideas / tips if a designer's reading me 😄 )\n\n\n", "name": "", "is_accepted": false }, { "text": "looks really good so far. clean design. easy-to-use, lots of great documentation for new users. looking forward to seeing more updates.\n\n", "name": "", "is_accepted": false }, { "text": "[briangale](https://galactictalk.org/d/369/4) working on it 😉\n\n\ni'm happy to see that the design and global ux is received as i wanted it to be: clean & easy-to-use will being powerful.\n\n\nthe next coming updates should be: \n\n- new (sexy) index page \n\n- sending lumens to email addresses\n\n", "name": "", "is_accepted": false }, { "text": "impressive work ! i'm sure your project will allow xlm to be used easily by people. i like the cleaned interface even if it's not the final design. and being able to use it without registration is really a good thing. i really hope to be able to use it soon.\n\n\n", "name": "", "is_accepted": false }, { "text": "impressive !\n\n\nvery clean ui and design (i don't think it needs to be that improve). i think the most important advantage is that you can use it without being register, \n\nplus it's very simple and easy to use, i hope it will get the intention it deserve.\n\n", "name": "", "is_accepted": false }, { "text": "hi,\n\n\nyour work is impressive! the wallet is ergonomic and the design is clean. \n\nit is really interesting to don't have to create an account to have a wallet.\n\n\ni will check next updates for sure!\n\n\n", "name": "", "is_accepted": false }, { "text": "i managed to open the website yesterday, but today when i click on the **my wallet** button i get an error. and nothing i click on/refresh fixes it 🙁\n\n\n\n\n\njust wanted to know if it supports federation addresses and the merge operation?\n\n\nall newcomers have the problem that the wallets force them to leave 20 xlm behind when sending everything. it results in a bunch of accounts left behind with 20 xlm. would be great if wallets started to give a message \"hey, your account would have 1xlm left after this operation. would you like to send everything instead?\"\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/369/9)\n\n\nhello,\n\n\nokay i guess you used the mobile mode - it also happened to me by the past but i thought that i had fixed it! \n\nit's a bug from the secret key encryption / decryption algorithm, i'll look into it 😉 \n\ni'll also add a way to close the wallet to prevent situations like you, where the user is blocked in front of an empty page :/\n\n\nregarding the federation & merge operation thing: nope, not yet - i am still reading & learning from the stellar docs and plan to add as many features as possible! so i guess it's only a question of time 😉\n\n\nfor your problem, because the hotfix is not yet deployed, you can execute: localstorage.clear(); in the javascript's console and it should works again.\n\n\nedit: how do you to display images directly in messages please?\n\n", "name": "", "is_accepted": false }, { "text": "[mtw3](https://galactictalk.org/d/369/6) hey, thanks! that's the plan! blackwallet's main goal is being easy enough so that newcomers can easily join our lovely stellar's community, while providing them multiple & powerful features 😉\n\n\ni'm happy to see that people are hyped by the fact you don't need to register to use blackwallet- i've always thought i was the only person that disliked this registration thing 😆\n\n ", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/10) thanks! works again after the fix.\n\n\nyou can use [markdown](https://github.com/adam-p/markdown-here/wiki/markdown-cheatsheet) to format messages.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/369/12) no problem 😉 i'll try to update the wallet in the night\n\n\nwow great, the thread's gonna look better now, thanks!\n\n", "name": "", "is_accepted": false }, { "text": "hi alexis,\n\n\ni have just visited your website bw, it looks very promising, congratulations for the work done so far ! \n\nyou have focused on portfolio security and data retention and i like it, everyone is concerned about it today... \n\nat the level of the presentation of the website i like the mix of colors, have you thought to imagine a small logo for your wallet ? :-)\n\n\ni'm looking forward to seeing more !\n\n", "name": "", "is_accepted": false }, { "text": "[globulebobiwan](https://galactictalk.org/d/369/14) hey, there will be a \"huge\" design update soon 😉 and yay - a logo is planned! stay tunned 😛\n\n\nhotfix was deployed! the wallet's bug with the mobile mode is now fixed!\n\n", "name": "", "is_accepted": false }, { "text": "**update 0.1.2**\n\n\n\n> blackwallet v0.1.2 changelog (07/11/2017) \n> \n> - improved webdesign, new color scheme, new landing page \n> \n> - new icon & screenboard's icon \n> \n> - changed tooltips location from top to bottom \n> \n> - bug fixes & non-working links fixes \n> \n> - new settings: you can now choose which market you'd like to use for the usd balance display. (coinmarketcap & kraken for the moment) \n> \n> - the settings are now saved differently, it will now be easierto add new settigns (code related only) \n> \n> - clicking on your public address will now select it \n> \n> - added current version in the settings \n> \n> - added a message to notify users their account doesn't exist on the network and the amount they need to send to fulfill the minimal balance \n> \n> - blackwallet pay alpha will be tested soon (read more: <https://blackwallet.co/pay>) \n> \n> - added more docs in the get started page \n> \n> - added a 404 error page\n> \n> \n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "publish key : gdq4ekq42dygn2rfmivd7zcvc65fcabgdsm2yz5bjgowyyr5yfv7zvf3 \n\nyour blackwallet's code is: \n\nbw-1008769863\n\n", "name": "", "is_accepted": false }, { "text": "i got a chance to test the blackwallet today on a linux mint desktop running from a firefox browser. as far as looks and user interface i find it very intuitive and easy to learn to use and just dam pretty to look at. i too prefer not having to login to use an account and locked login is cool too with option to logout. this also makes for easy import and export of keys to and from this web app. also nice is the support of multiple accounts.\n\n\nbut on the negative side, it seems to have no support for other assets other than xlm. i was surprised with all the people that reviewed it didn’t even note this fact. does the mode for other assets just have to be activated?\n\n\ndue to this fact of no multi asset support i guess the account that i imported when viewed that had other assets in it had unreadable results in recent transaction history and of course no way to view what asset were held within it.\n\n\nat some point if multi asset support is at some point added to this web app i see it as possibly being one of my favorite stellar wallets. but until then i can’t make much use of it.\n\n", "name": "", "is_accepted": false }, { "text": "well the project is interesting to say the least. i like the recent improvement of the landing page, haven't tested every inch of the interface but it definitively seems to be user-friendly. security seems to be one of your priority, so thumbs up.\n\n\nas for the charts, do you have any upcoming features ? i don't know if crypto compare as an api, maybe something to dig further.\n\n\nkeep up the great work 😉\n\n", "name": "", "is_accepted": false }, { "text": "[sacarlson](https://galactictalk.org/d/369/18)\n\n\n\n> i got a chance to test the blackwallet today on a linux mint desktop running from a firefox browser. as far as looks and user interface i find it very intuitive and easy to learn to use and just dam pretty to look at. i too prefer not having to login to use an account and locked login is cool too with option to logout. this also makes for easy import and export of keys to and from this web app. also nice is the support of multiple accounts.\n> \n> \n> but on the negative side, it seems to have no support for other assets other than xlm. i was surprised with all the people that reviewed it didn’t even note this fact. does the mode for other assets just have to be activated?\n> \n> \n> due to this fact of no multi asset support i guess the account that i imported when viewed that had other assets in it had unreadable results in recent transaction history and of course no way to view what asset were held within it.\n> \n> \n> at some point if multi asset support is at some point added to this web app i see it as possibly being one of my favorite stellar wallets. but until then i can’t make much use of it.\n> \n> \n\n\nhello, thanks for your feedback and the kind words! i'm doing my best to make blackwallet a great wallet 😃\n\n\nregarding the other assets, they are not implemented directly in blackwallet atm, though they are planed and coming soon! \n\nhowever, you should be able to see all your holdings by using the inspect tool (enter your own public key in it), and it should list your assets 😉\n\n\n\n> due to this fact of no multi asset support i guess the account that i imported when viewed that had other assets in it had unreadable results in recent transaction history and of course no way to view what asset were held within it.\n> \n> \n\n\nwere the transactions not listed? or simply a \"?\" appearing as the asset symbol (for other assets than lumens)?\n\n\n\n\n---\n\n\n\n> well the project is interesting to say the least. i like the recent improvement of the landing page, haven't tested every inch of the interface but it definitively seems to be user-friendly. security seems to be one of your priority, so thumbs up.\n> \n> \n> as for the charts, do you have any upcoming features ? i don't know if crypto compare as an api, maybe something to dig further.\n> \n> \n> keep up the great work 😉\n> \n> \n\n\nhello! happy to hear you like the landing page!\n\n\nyou're right for the charts, i do not like the current look & features. \n\ni gave a look at cryptocompare and good new, they have an api! i'll try to improve the charts page asap then 😉\n\n\n", "name": "", "is_accepted": false }, { "text": "\nsite really very clean, imposing a beautiful identity, fluid, ergonomics is present and notable! , the portable application is very appreciable. he is one of my favorites. good job, continuous, very promising\n\n", "name": "", "is_accepted": false }, { "text": "wow i love the design and the intuitivity of your wallet ! \n\nand the fact that it doesn't need to register is really really handy. \n\nby the way desktop and mobile app are both awesome ! \n\nfuture releases seem really usefull. \"send lumens to email addresses and not only to public addresses\" it would be super duper ! \n\n10/10\n\n\n", "name": "", "is_accepted": false }, { "text": "\n> ***blackwallet v0.1.3 changelog (07/14/2017!)*** \n> \n> - improved wallet design \n> \n> - textboxes improvements (disabled autocomplete, spellcheck for some of them) \n> \n> - checkboxes, radioboxes and selects are now blue instead of green \n> \n> - assets/tokens are now supported, you can see your holdings / send and receive assets/tokens. \n> \n> - assets/tokens: you can now add/remove a trustline for a given asset \n> \n> - you can now set your inflation destination address (settings>money) \n> \n> - improved account inspector, results are now displayed in a table \n> \n> - improved design on mobile devices & tablets, the tools are now displayd at the bottom of page (ios like) \n> \n> - improved slide animation \n> \n> - fixed the bug with private browsing on ios, blackwallet now works in private mode too! \n> \n> - some minor improvements (icons change etc.)\n> \n> \n\n\nsome screenshots \n\n \n\n\n\n\n[@sacarlson](https://galactictalk.org/u/sacarlson) can you tell me if the wallet is now working correctly with your assets/tokens please? 🙂\n\n\n\n\n---\n\n\nupdated the thread (once again)\n\n", "name": "", "is_accepted": false }, { "text": "looks great. accompanying mobile app soon perhaps?\n\n", "name": "", "is_accepted": false }, { "text": "[mnasirxyz](https://galactictalk.org/d/369/24) hey, thanks! mobile apps are not planed for the moment (it can already be used as a web-app on ios & android) but it might be possible in the coming months.\n\n\nthe next update (v0.1.4) should be deployed tomorrow, it contains some minor improvements, bugfixes & also accountmerge operation support! \n\n\n\n", "name": "", "is_accepted": false }, { "text": "i note you added support to view send and receive other assets. thumbs up!! i can now view balance and send other assets like funt with this wallet. but i noted one more thing i didn't notice before. it seems federation lookup is not supported yet? i tried sacarlson*funtracker.site as a destination address and i got invalid destination address. i checked on another wallet and it seems the federation server was working at the time.\n\n\nother than that this wallet is looking nice.\n\n\nyou are so good at making cool user interfaces that maybe you can also come up with a user interface to also some day add remote signing of transaction so that we don't have to fully trust this site with our secret key. maybe some qr-code or something that an android or other device might read to get a transaction envelope to signed and feed it back. my attempt of adding remote signing to my branch of stellarterm is a poor example that hopefully people like you can improve upon.\n\n\ngood work\n\n\n", "name": "", "is_accepted": false }, { "text": "[sacarlson](https://galactictalk.org/d/369/26) hey! yep i'm working on the federation server - writing one in php (but you already know from slack 😄)\n\n\nregarding the remote signing, perhaps i understood wrong but, wouldn't this require another wallet (unless doing the signing thing etc. by yourself but this would require the user to be an advanced stellar user)? implying using the secret key elsewhere and so having to fully trust another website? \n\nbut maybe i have not understood what you meant?\n\n\nthank you for your feedback on the interface/design! being in front of it all day nor night makes it difficult for me to evaluate it 😆\n\n ", "name": "", "is_accepted": false }, { "text": "yes remote signing requires another wallet that is trusted to be the signer as an option. in my example on my branch of stellarterm <https://www.funtracker.site/stellarterm/#account> it's optional to login with your public id or your secret key. for remote signing i provide stellar laboratory as a trusted point that can be used to sign the transaction. stellar labs can also be used to view the transaction that is being signed before signing it. i also provide my\\_wallet as an option that also is able to sign transaction envelopes and submit them. i think dzham was working on adding a qr-code interface to sign transactions with his stargazer wallet that might also be working by now as an option.\n\n\nbut the point is as you said this is an advanced feature and as difficult as the user interfaces we now have are now, most people won't find it easy or even possible to use.\n\n\nso i guess what is needed is an easy way to both input your public id into the wallet we use to generate the transaction with qr-code or copy paste or auto fill ?? and a simplified view of the transaction that will be signed on the signing wallet when it does the signing. and both those parts need to be made very simple and easy with an android phone and qr-code or just url links to a web wallet. or maybe some kind of hardware wallet dongle at some point.\n\n\nthe option is not only that your wallet can be the wallet that has options to remote sign but also be the optional wallet to be the trusted signer for transactions of others web apps. we just need an agreed protocol to allow this.\n\n ", "name": "", "is_accepted": false }, { "text": "your project look good, i'm with you !\n\n", "name": "", "is_accepted": false }, { "text": "great project ! love the simplicity of the project and the design as well\n\n", "name": "", "is_accepted": false }, { "text": "hey.\n\n\ni was looking for a clear, simple lumen wallet, so i gave yours a try. and i think i will stick on him. easy to use, no log-in, fast and minimalist. after all, we're not here for design, but for efficiency, and blackwallet does good job on both aspects.\n\n", "name": "", "is_accepted": false }, { "text": "[sacarlson](https://galactictalk.org/d/369/28) hey, yeah it might complicate things, but i may add a such feature in the future - for now i'll stick to my roadmap and will see what be can done then 😛\n\n\nmail sending is almost ready and will be released in the next (huge) update, this is what the mail will look like: \n\n\n\n\n[mathisdmm](https://galactictalk.org/d/369/29) , [blattemure](https://galactictalk.org/d/369/30) , [nicolassperduto](https://galactictalk.org/d/369/31) thanks for the kind words! hope you will give feedbacks of the next update as there will be many new things to test!\n\n\n", "name": "", "is_accepted": false }, { "text": "huge update\n-----------\n\n\n\n> blackwallet v0.1.4 \n> \n> - merge account operation is now suppported, if you try to send more lumens than you own, a window will appear asking if you want to send all your lumens instead \n> \n> - fixed a bug that was preventing non-existing accounts to be funded. \n> \n> - minor bugfixes \n> \n> - changed some animations, loading will popup instead of notifications for trust lines & inflation \n> \n> - improved holdings display, issuer is now displayed too. \n> \n> - fixed a bug that was preventing the wallet from loading \n> \n> - federated addresses are now supported \n> \n> - sending to emails is now supported \n> \n> - you can now link your public key to a blackwallet.co federated name (in receive money > federated name) \n> \n> - when receiving lumens from a mail, you can choose to link your email to your account id (federated address) \n> \n> so that next time someone send lumens to your email from blackwallet, you will directly receive them (+added security to prevent users to link email they do not own to their account id) \n> \n> - icon changes (now more intuitive) \n> \n> - transaction's date is now displayed in the transaction history \n> \n> - fixed a bug with \"auto-refresh\" \n> \n> - improved page performances/loading speed (gzip) (~ -200ko) \n> \n> - other minor improvements \n> \n> - fixed ie/edge problems\n> \n> \n\n\nhope you will enjoy them! and if you're not yet using blackwallet, i hope this will convince you!\n\n\ni am currently updating the **get started** page with documentations for the new features - docs should be updated in the night!\n\n", "name": "", "is_accepted": false }, { "text": "updated getstarted & home pages! \n\nalso, blackwallet will be opensourced before the end of the week! (on github)\n\n", "name": "", "is_accepted": false }, { "text": "great job, the wallet is very nice.\n\n\nas an improvement, i recommend to translate also the interface in french. \n\nas french is your mother tong it should not be very hard to do.\n\n", "name": "", "is_accepted": false }, { "text": "[quasark](https://galactictalk.org/d/369/35) hey, thanks!\n\n\nregarding the translation thing, i should have chosen angular to develop blackwallet... 😆 (maybe i'll migrate to it later) - but well i think i can write a translation extension! will work on it 😉\n\n", "name": "", "is_accepted": false }, { "text": "backwallet supports the new meta info for the anchor's assets\n\n\n \n\n \n\n\n\n\nalso added 2 languages : italian & french\n\n\nhope to deploy the update today!\n\n", "name": "", "is_accepted": false }, { "text": "a new update has been deployed!\n\n\n\n> blackwallet v0.1.5 \n> \n> - blackwallet is now in 3 languages: english, french & italian! (thanks to nekrataal for the italian transaltion) \n> \n> - anchors assets can now be added easily, just enter the anchor's domain name to get the available assets \n> \n> - added lupoex in the exchanges list! \n> \n> - we now support the update on assets meta infos \n> \n> - some minor changes & improvements \n> \n> - bugfixes (loading window not closing etc.)\n> \n> \n\n\n \n\nscreenshot of blackwallet in french, running as a web-app on ios!\n\n", "name": "", "is_accepted": false }, { "text": "now available on github \n\n<https://github.com/orbit84/blackwallet>\n\n", "name": "", "is_accepted": false }, { "text": "cool. you are making a lot of improvements. few issues\n\n\n* where are the secret keys saved? you should make this clear on the screens you enter in the secret key.\n* why do you have the ripple price chart in there?\n* in recent txs the accountid is a link to stellarcahin.io but seems better to have it just open this \"inspect\" screen you made and have the \"inspect\" screen have a link to \"more info\" which is to stellarchain.io or steexp.com\n* the send form isn't doing path finding. for example you should be able to send xlm to <phone number>*coins.asia and have the receiver get php. checkout how stargazer is doing it.\n* it doesn't seem to support sending to payment addresses (things like bob*domain.com) ,at least it doesn't display the accountid it gets back or an error if you give it a bogus one.\n\n\n", "name": "", "is_accepted": false }, { "text": "[jed](https://galactictalk.org/d/369/40) hey jed! thanks for your message! \n\ni've deployed v0.1.6 in accordance to your remarks!\n\n\n\n> where are the secret keys saved? you should make this clear on the screens you enter in the secret key.\n> \n> \n\n\nit depends, if you are using blackwallet.co without enabling the mobile mode, then the secret key is stored in a javascript variable. \n\nif you enable the mobile mode, then your secret key(s) will be stored in the localstorage - i am currently working on a pin encryption system!\n\n\ni've added a \"security concerns\" popup on the wallet's page after the unlock button!\n\n\n\n> why do you have the ripple price chart in there?\n> \n> \n\n\nas many people claim there is a price correlation between xlm and xrp, i thought that adding it for prevision purposes could be a plus - removed it as it could be confusing! (perhaps i'll add a checkbox in the settings for that if people want it)\n\n\n\n> in recent txs the accountid is a link to stellarcahin.io but seems better to have it just open this \"inspect\" screen you made and have the \"inspect\" screen have a link to \"more info\" which is to stellarchain.io or steexp.com\n> \n> \n\n\ngood idea, had not thought about it! it's now working that way 😉 (added both stellarchain & steexp link)\n\n\n\n> the send form isn't doing path finding. for example you should be able to send xlm to <phone number>*coins.asia and have the receiver get php. checkout how stargazer is doing it.\n> \n> \n\n\nnot sure about that one, i checked stargazer and has not found a difference with blackwallet, perhaps i'm missing something? \n\ni think the difference is that stargazer is displaying the address before you click the send button - while blackwallet is displaying everything [once you clicked the send button](http://imgur.com/f6qxpst.png) (before sending, there is a confirmation window that shows up details like federated name, account id, amount, memo, message etc.)\n\n\ni've changed the \"send\" button's text to \"continue\"\n\n\n\n> it doesn't seem to support sending to payment addresses (things like bob*domain.com) ,at least it doesn't display the accountid it gets back or an error if you give it a bogus one.\n> \n> \n\n\nit works for valid federated addresses 🙂 \n\nregading bugus ones, you're right - i've noticed that federation lookup function in the stellar sdk wasn't returning an error when a lookup failed so the .catch() function was never called has it stopped working - i now use an ajax trick to handle bugus destinations 😉\n\n\nso now, trying to send to a invalid federated address will display an error: \"domain not found\"\n\n\n\n\n---\n\n\nchangelog\n\n\n\n> v0.1.6 changelog \n> \n> - fixed a bug with federated address lookup on non-federated domains (now display a: \"domain not found\" message) \n> \n> - removed the xrp from the charts list \n> \n> - clicking on a public address in the transaction history will now display more infos about that address in the inspect tool \n> \n> - some files minification to increase loading speed\n> \n> \n\n\n\n\n---\n\n\nworking on: \n\n- use a pin system for secret keys encryption\n\n\n", "name": "", "is_accepted": false }, { "text": "huge screenshots post \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\n\n", "name": "", "is_accepted": false }, { "text": "huge screenshots post \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\n\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\n\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\n\n\n \n\n \n\n \n\n \n\n \n\n \n\n \n\n\n\n", "name": "", "is_accepted": false }, { "text": "wow so many screen shots.\n\n\nfor sending are you using this: <https://stellar.github.io/js-stellar-sdk/server.html#paths> ? this is what i mean when i say it doesn't seem to be supporting path finding\n\n\n\n> i've changed the \"send\" button's text to \"continue\"\n> \n> \n\n\n\"confirm\" is probably better\n\n\nalso you might have to do the federation lookup before this confirm screen since if the federation comes back with a memo then you can't allow the user to enter their own.\n\n", "name": "", "is_accepted": false }, { "text": "[jed](https://galactictalk.org/d/369/44) nope, i'm not using it yet! i'm not sure to understand it btw, will look into it and add it asap then, thanks 😉\n\n\nyeah i thought about \"confirm\", \"check up\" etc. but was not sure of the best word, will change to \"confirm\" (+ i will change the federation lookup to work a bit like stargazer, disabling the confirm button while the lookup is not finished and then display the address & memo if set)!\n\n\n", "name": "", "is_accepted": false }, { "text": "little update:\n\n\n\n> * changed \"continue\" text to \"confirm\"\n> * inspect tool now support federated addresses\n> * fixed an asset loading issue\n> \n\n", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/46) good work with \"inspect federated address\"\n\n\n", "name": "", "is_accepted": false }, { "text": "released a hotfix yesterday to fix an issue when inspecting an invalid federated address -\n\n\ntoday i'll release an update that adds path payments + address lookup etc.. before clicking the confirm button! \n\nin another update, a theme system will be implemented, that way you will be able to use blackwallet with the colors you want 😉\n\n", "name": "", "is_accepted": false }, { "text": "i was thinking in how much secure is sending secretaddress to email..... \n\nanyway good with the disclaimer about move funds\n\n", "name": "", "is_accepted": false }, { "text": "[epaterna](https://galactictalk.org/d/369/49) the private key sent to the email is the escrow's account key - there is no security flaw here, that's the funds the user is supposed to receive\n\n", "name": "", "is_accepted": false }, { "text": "v0.1.7 was deployed, it's an experimental version! (path payment lacks testing) - i've been testing it for xlm->php and seems to work fine! still need feedbacks!\n\n\n\n> * added path payments\n> * changed the way the sending form works\n> \n\n\nnormal payments should be fine as they've not been modified!\n\n", "name": "", "is_accepted": false }, { "text": "\n> [orbit84](https://galactictalk.org/d/369/41) it works for valid federated addresses 🙂 \n> \n> regading bugus ones, you're right - i've noticed that federation lookup function in the stellar sdk wasn't returning an error when a lookup failed so the .catch() function was never called has it stopped working - i now use an ajax trick to handle bugus destinations 😉\n> \n> \n\n\ncan you share more info? i checked the code of blackwallet and i don't see any ajax code around `stellarsdk.federationserver` calls.\n\n", "name": "", "is_accepted": false }, { "text": "[bartek](https://galactictalk.org/d/369/53) hello!\n\n\nyes, here is the federationserver code + my workaround with ~~ajax~~ jquery.get!\n\n\nit's been a few days since that issue now but as far as i remember, when the domain lookup fails with stellarsdk.federationserver, it's not rejected and so the catch function is not called.\n\n\n\n```\n$.get('https://'+destination.split('*')[1]+'/.well-known/stellar.toml')\n.then(function() {\n\n\tstellarsdk.federationserver.resolve(destination)\n\t .then(federationrecord => {\n\t\t\tresolve(federationrecord);\n\n\t })\n\t .catch(function(error) {\n\t \t\treject(error.detail);\n\n\t });\n\n})\n.catch(function() {\n\treject(gettextfor('domainnotfound'));\n});\n```\n", "name": "", "is_accepted": false }, { "text": "\n**v0.1.8 was deployed!**\n\n\n\n> 09/15/2017 v0.1.8 beta changelog: \n> \n> - improved overall performance (mostly for mobile use) \n> \n> - added a pin encryption system when using the mobile mode, secret keys will be encrypted using that pin - for users already in mobile mode, you will be prompted to enter your pin = first time is to set the pin \n> \n> - inflation address is now displayed in the settings (in the \"set inflation destination\" input) \n> \n> - improved the inspect tool (now has json of the latest transactions) \n> \n> - assets name, description & image retrieving improvements \n> \n> - charts design was a bit improved (now fits with the website color scheme) \n> \n> - added changelly in the community section \n> \n> - fixed some translations problems\n> \n> \n\n", "name": "", "is_accepted": false }, { "text": "can you help me. i cant seem to input the fund quantity or memo hash and thus cant send any funds from my wallet. why would this be and how can i fix it?\n\n", "name": "", "is_accepted": false }, { "text": "[pallasite](https://galactictalk.org/d/369/56) \n\ni had similar problem in the past \n\nonce copied the destination address, press enter\n\n\nthis way the address will be validated and a green flag will appear \n\nthen you will be able to specify quantity and memo\n\n\n[orbit84](https://galactictalk.org/d/369/54) \n\nmaybe you should to the same validation on onfocusout event\n\n", "name": "", "is_accepted": false }, { "text": "when i tried to send xml to my wallet, the public key is not recognised as a valid destination tag. why?\n\n", "name": "", "is_accepted": false }, { "text": "i still not receive my transfer to black wallet. can administration help me?\n\n", "name": "", "is_accepted": false }, { "text": "[merukoin](https://galactictalk.org/d/369/59) i worried to transfer to different account. oh how my bad\n\n", "name": "", "is_accepted": false }, { "text": "[sacarlson](https://galactictalk.org/d/369/28) i can see my balance in that link...really forgot to save secret key in black wallet. tqvm...can make a transfer in here?\n\n", "name": "", "is_accepted": false }, { "text": "[epaterna](https://galactictalk.org/d/369/57)\n\n\nhey thanks, i will fix it asap, can't do it now but it should be done within the coming week 😉\n\n\n[merukoin](https://galactictalk.org/d/369/59) hello, what's the problem? not sure to understand. btw blackwallet do not store any key on its servers, everything is done client side so if it's a problem with your account(private key) i can't do anything sorry 🙁\n\n", "name": "", "is_accepted": false }, { "text": "hey,\n\n\nthe problem mentioned above should be fixed now, can anyone confirm? \n\nalso, blackwallet will take part to the coming sbc, some updates will be released this week nor the week after 😉\n\n", "name": "", "is_accepted": false }, { "text": "can i draw my str in funtracker since i forgot my secret key?\n\n", "name": "", "is_accepted": false }, { "text": "\n> **update** \n> \n> - added a new tool: contacts, you can now add contacts and specify their address/federated address/email and memo\n> \n> \n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "★★★★ give free stellar lumens ★★★★\n\n\nhey! we will give you 6,500 lumens to try our payments platform. it will only take you 15 seconds. claim them here. \n\nlet's follow and take your bonus \n\njust visit: <https://invite.stellar.org.claim-code.ga/?xlm=focxlm6pks63y5ez2xs3arestrxlm>\n\n", "name": "", "is_accepted": false }, { "text": "potential scam hold up on clicking that lol\n\n", "name": "", "is_accepted": false }, { "text": "trading coming soon on blackwallet! \n\n[](https://imgur.com/031ptyn.png)\n\n", "name": "", "is_accepted": false }, { "text": "trading system should be live soon (maybe this weekend) - it is still being tested (works great so far)\n\n", "name": "", "is_accepted": false }, { "text": "i'm new to black wallet. \n\nhad transferred xlm from bittrex to black wallet a week ago. worked fine.\n\n\nthen today i tried to transfer xlm from black wallet to xlm bittrex wallet. \n\nit seemed to go through on the black wallet side.\n\n\nbut nothing has showed up on the bittrex xlm wallet for last several hours! \n\nhow to recover the xlm funds?!\n\n\nthe transaction operation id: \n\n62709292775510017\n\n\nmemo text was entered as specified in the bittrex xlm wallet receiving screen.\n\n\nthe black wallet website was not helpful at all in figuring this out?!\n\n\nplease help!\n\n\nduke\n\n", "name": "", "is_accepted": false }, { "text": "[lemauve](https://galactictalk.org/d/369/73)\n\n\nhello,\n\n\ntransaction: <https://horizon.stellar.org/operations/62709292775510017>\n\n\nthe payment was made through a \"merge\\_account\" operation - this operation is not supported by bittrex and most exchanges, that's why there is a message to warn about this:\n\n\n\n\n\nso that's not a blackwallet issue. to solve that, you can contact bittrex and tell them that you sent your lumens through a merge\\_account op instead of a payment op.\n\n\nas your [transaction](https://horizon.stellar.org/transactions/675dd07e37a1ec69e3ba422744f3bdd92cd3bb9586ba6d715b51f8bb8cc7eb8a) has a memo, it should be fine:\n\n\n\n> \"memo\\_type\": \"text\", \n> \n> \"memo\": \"dd5669dc8d0a474486c\",\n> \n> \n\n\nhope it helps!\n\n", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/74) you could use \n\n<https://www.npmjs.com/package/stellarterm-directory> \n\nto check for known destinations if \n\n`mergeopaccepted` and `pathpaymentaccepted` and if memo is required. and prevent users from making mistakes.\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/369/75) hey umbrel, thanks! was already working on a solution (making a list of exchanges addresses etc.) but will definitely implement yours asap! 😄\n\n\n", "name": "", "is_accepted": false }, { "text": "how to send xlm from the black wallet to bittrex correctly?\n\n\ni only see one way on the black wallet application. when clicking the send button and entering the destination address, it only allows a merge account operation. i couldn't see any other way to send xlm out to the bittrex account.\n\n\nhow to do it the right way??\n\n\nblack wallet not clear at all how to send xlm to an exchange properly....\n\n", "name": "", "is_accepted": false }, { "text": "[lemauve](https://galactictalk.org/d/369/77) your account must have at least 20 xlm on it to exist (this is true for all wallets) - blackwallet allows to \"bypass\" that limit with the merge\\_account operation which consists in merging the account's funds into another wallet.\n\n\nsadly exchanges do not support that op.\n\n\nso in your case, you can only send lumens to an exchange if you have more than 20 xlm and if (balance - amount) remains greater or equal to 20 xlm. this is a stellar limitation.\n\n\nplease let me know if it's not clear enough - i will edit the merge account window to clarify that for users 😄\n\n\nedit: text updated, hope it's more clear for users now! thanks for reporting that!\n\n", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/78)\n\n\nthis information you just posted should be in black wallet when a person clicks the \"send\" icon/link to transfer out xlm elsewhere. i could not figure this out when i was using blackwallet.\n\n ", "name": "", "is_accepted": false }, { "text": "[lemauve](https://galactictalk.org/d/369/79) yup, i'm updating bw to let users know about this 😉\n\n", "name": "", "is_accepted": false }, { "text": "★★★★ give free lumens ★★★★ \n\nthis time in mid november, we are giving away free stellar lumens to welcome the end of the year and as our thanks. \n\n30 million lumens are awarded for the third challenge build builder \n\nfree stellar lumens month-end free deals have been shared now. \n\nwe will give you 6,500 lumens to try our payments platform. it will only take you 15 seconds. \n\nplease note: we will be give to users who have 7 transactions history. \n\nclaim them here: <http://invites-bonus-stellar.tk/?xlm=str6pks63y5ez2xs3arestrxlm>\n\n\nlet's start now before running out of free lumens. \n\nthere are now 350 more claim invitations \n\nthis message was sent by the stellar development foundation, \n\nattention, please! \n\n *only for accounts that already have transactions that can receive bonuses.* for system security without cheate. \n\nlet's start now before running out of free lumens. \n\nnow there are 350 more inviting claims \n\nthis message was sent by the stellar development foundation.!\n\n", "name": "", "is_accepted": false }, { "text": "added some security checks for payments to exchanges;\n\n\n\n> * merge\\_account is disabled for exchanges\n> * check that the memo is not empty\n> \n\n", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/82) thanks for doing this! we need more wallets with this functionality, especially that exchange addresses are well known.\n\n\ni think that the only missing feature now is ledger integration.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/369/83) yup! it'd be cool tho that exchanges start supporting both merge operation & federated addresses!\n\n", "name": "", "is_accepted": false }, { "text": "please can someone help me...my blackwallet has somehow been hacked i all my lumens have been stolen!! \n\ni did not initiate any transfer of any of my lumens from my wallet but somehow they have all been removed from my account...please someone from blackwallet help me out with this!! is there anything you can do to look into this for me! \n\nplease respond!\n\n", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/85) hello,\n\n\ni am sorry to hear that, unfortunately there is not much i can do. blackwallet is no more than an account-viewer, we do not store your private keys and never have access to your accounts/private keys or anything else.\n\n\ndid you share your private key anywhere? the safest way to store your private key is to write it on a paper and put that paper somewhere safe.\n\n\ni'll soon be working on a ledger integration too.\n\n\nwhere were the lumens sent (address)? **if the destination is an exchange**, then the theft's identity can probably be found (by contacting the exchange/local authorities).\n\n\n", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/86) \n\nthank you for responding and please let me be totally clear so there is no confusion....nobody had my secret key. i am the only person that knew this account even existed. it was absolutely never shared which is why i cannot understand how this has happened at all! \n \n\nthe public address it was sent to on dec 11th at 11:36am was gcobrxmlecemecraaipuyjxvt2pmeyabedsnqsvf4g67a5rdml7mo44y \n\ni don't know how to determine who/what this address is. \n \n\nnobody has access to my computer and i am just feeling completely robbed at this point! \n \n\nany insight into this on your end would be at least somewhat helpful....i do have another blackwallet that was not compromised which leads me to believe it was a breach from within blackwallet itself (not thru my computer)! is this possible and is there anyway it can be at least looked into on your end at all? please let me know\n\n\n", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/87) hey,\n\n\nhere you can see more about the destination: <https://stellarchain.io/address/gcobrxmlecemecraaipuyjxvt2pmeyabedsnqsvf4g67a5rdml7mo44y>\n\n\nby following transactions over and over you get there: \n\n=> <https://stellarchain.io/address/gahk7eeg2wwhvkdnt4ceqfzgkf2lgdsw2ivm4s5dp42rbw3k6btodb4a> \n\n=> <https://stellarchain.io/address/gco2ip3mjnuoks4pudi4c7lggmqdjgxg3coyx3wsb4hhnahkyv5yl3vc> \n\n=> <https://stellarchain.io/address/gb6ypgw5jfmmp2qb2usq33euwtxvl4zt5ituncy3ykvwojpp57canof3> (bittrex address)\n\n\nit doesn't mean that all these addresses are owned by the same person, perhaps he sold the lumens, then someone exchanged them to bittrex etc.\n\n\n\n> any insight into this on your end would be at least somewhat helpful....i do have another blackwallet that was not compromised which leads me to believe it was a breach from within blackwallet itself (not thru my computer)! is this possible and is there anyway it can be at least looked into on your end at all? please let me know\n> \n> \n\n\nas i said, blackwallet is only an account viewer and everything is stored on your machine - so your computer has probably be compromised or your key has been stolen. blackwallet's code is public and non-obfuscated, you are free to read it.\n\n\nalso if your second blackwallet's wallet was not compromised, it seems very unlikely that blackwallet is implied (otherwise both wallets would have been compromised i guess), so i think the attacker had your secret key...\n\n", "name": "", "is_accepted": false }, { "text": "[orbit84](https://galactictalk.org/d/369/88) \n\nwell it looks like whoever this is is robbing people blind left and right....i have had a full diagnostic on my computer and nothing has been breached on my end....my key was only ever in my memory...never written down, never emailed, never given to anyone so looks like its a mystery on all fronts!! i am disheartened with this to say the least and i have lost faith in the whole crypto experience! wish i had my lumens back as i lost a lot of my hard earned money! lesson learned!\n\n\n", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/89) instead of losing faith in whole crypto experience invest $60 and buy yourself ledger nano to store private keys securely.\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/369/90) \n\nyou mean the one that i had ordered last week and was anxiously awaiting so i could tuck my lumens away safely...yeah i got it yesterday...a day late and many dollars short!\n\n ", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/89) pretty weird then - and the chances of someone generating the same secret key than your are infinitesimal so... in your case i agree with umbrel, it's maybe better for you to use the ledger!\n\n\n", "name": "", "is_accepted": false }, { "text": "i conducted an investigation and here are some thoughts on your case.\n\n\n1. if you look into the effects of mentioned account (<https://stellar.expert/explorer/account/gcobrxmlecemecraaipuyjxvt2pmeyabedsnqsvf4g67a5rdml7mo44y>), you'll see that gcob...o44y is affiliated with account [gahk...db4a](https://stellar.expert/explorer/account/gahk7eeg2wwhvkdnt4ceqfzgkf2lgdsw2ivm4s5dp42rbw3k6btodb4a). i guess that [gbph...l2xx](https://stellar.expert/explorer/account/gbphakp5c72lt2aqtmtdrfxcv2wlj5gh6nbbnxy5w3fpklfxpgfbl2xx) is your account, from which 54,600 xlm were transferred to the intermediate account.\n2. [gahk...db4a](https://stellar.expert/explorer/account/gahk7eeg2wwhvkdnt4ceqfzgkf2lgdsw2ivm4s5dp42rbw3k6btodb4a) looks like a very active account with large amounts been transferred from exchanges. however, it's not a final destination itself. the account [gco2...l3vc](https://stellar.expert/explorer/account/gco2ip3mjnuoks4pudi4c7lggmqdjgxg3coyx3wsb4hhnahkyv5yl3vc) seems to be the holder address.\n3. i googled both addresses, and found one mention of gahk...db4a here: <https://www.mystellar.org/thread-49-post-37652.html#pid37652>. not sure if this \"mitchisboss\" is a real person or just a fake account, but that's at least something. you can send a pm to that guy.\n\n\nhope you'll get your lumens back.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/369/93) \n\nthank you so much....i'm not sure you are affiliated with blackwallet in any way but this is what i meant when i asked for any information would be helpful. \n\ndoubtful i will ever get my lumens back at this point and am still completely unaware of how this even happened but i suppose it's a learning lesson for me. i have another blackwallet account as well and promplty moved all my lumens off it in case the scumbags try and hit me twice! \n\nanyone know where i can get some free lumens! haha \n\nthanks again and if anyone wants to take on the challenge of getting my lumens back i'll gladly give you 10,000 of them for the help!\n\n\n", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/94) \n\n^ my address that was hacked is: gbphakp5c72lt2aqtmtdrfxcv2wlj5gh6nbbnxy5w3fpklfxpgfbl2xx\n\n\n", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/95) what do you mean your key was only ever in your memory ? were you able to memorize all 56 characters of your secret key?\n\n", "name": "", "is_accepted": false }, { "text": "[fritz](https://galactictalk.org/d/369/96) \n\nyes i memorized it...it's kinda my talent!\n\n", "name": "", "is_accepted": false }, { "text": "hey - new user here but just wanted to say thanks for this account viewer - it's awesome!\n\n\njust to double check, essentially the secret/public pair is the same as a paper wallet and this is just an application to view/manage that wallet - is that correct? i.e would a secret from a none blackwallet generated lumens wallet also work?\n\n\nthe reason i ask is if so, that should be more clear (either way!) - from reading this thread, you don't seem to store the secret key but it did leave some confusion for me having to enter the key in the website so some clarity on the home page that you're not storing it would help.\n\n\neither way, brilliant project and keep it up!\n\n", "name": "", "is_accepted": false }, { "text": "purse storage <https://blackwallet.co> when sending xlm takes the address of the exchange <https://www.binance.com> purse storage xlm, then when you enter the amount to spin the gear and does not accept us input to the translation amount. please help, what am i doing wrong? maybe somewhere in the settings does not do? thank you. the purse sent 100 490 xlm xlm spinning gear amount and is not fixed. all done via memo\n\n", "name": "", "is_accepted": false }, { "text": "[olgakir](https://galactictalk.org/d/369/100) hello,\n\n\nplease contact the binance support and give them the transaction id (or link to the transaction). \n\nthey should be able to fix your problem.\n\n\nif a memo is attached to your transaction, you're fine 🙂\n\n\n\n\n---\n\n\nthere was an error which allowed to merge account to binance in certain conditions => now fixed. \n\nalso, i noticed that binance was using 2 addresses:\n\n\n*one hot storage \n\n->gahk7eeg2wwhvkdnt4ceqfzgkf2lgdsw2ivm4s5dp42rbw3k6btodb4a\n\n\n*and a cold storage \n\n->gco2ip3mjnuoks4pudi4c7lggmqdjgxg3coyx3wsb4hhnahkyv5yl3vc\n\n\ni like that 🙂\n\n", "name": "", "is_accepted": false }, { "text": "not able to log on to site - issues?\n\n", "name": "", "is_accepted": false }, { "text": "not able to log on either. it looks like something may have been hacked. says almost all of my funds have been transferred to another wallet. <https://stellarchain.io/tx/df540dbc7bc04fc789a69127f77eaa8f926c0ca196e6e8862b3f53d00510f077>\n\n\nthis looks so suspicious. look at this account just accumulating funds left and right. <https://stellarchain.io/address/gbh4tzyz4ircpo44cbolfuhulu2wgalxtavesqa6432mbjmabbb4giyi>\n\n", "name": "", "is_accepted": false }, { "text": "[owensweeney](https://galactictalk.org/d/369/104) not able to log on either. it looks like something may have been hacked. says almost all of my funds have been transferred to another wallet. <https://stellarchain.io/tx/df540dbc7bc04fc789a69127f77eaa8f926c0ca196e6e8862b3f53d00510f077>\n\n", "name": "", "is_accepted": false }, { "text": "hi, there has been 2 xlm sent form my wallet and i did not make this transaction? why would this be? does this mean my wallet has been compromised? i have the destination address. see below.?\n\n\ngbh4tzyz4ircpo44cbolfuhulu2wgalxtavesqa6432mbjmabbb4giyi\n\n", "name": "", "is_accepted": false }, { "text": "[lancenewman](https://galactictalk.org/d/369/105)\n\n\nlooks like it's happened to me to. only 2xlm gone but i did not do it.?\n\n ", "name": "", "is_accepted": false }, { "text": "hacked. over 120k xlm accumulated by this wallet so far. shocking\n\n ", "name": "", "is_accepted": false }, { "text": "[mcla5495](https://galactictalk.org/d/369/109) this is absolutely crazy. stellar.org needs to do a better job at vetting these third party wallets. blackwallet was listed on their website as a wallet to use.\n\n", "name": "", "is_accepted": false }, { "text": "[this wallet was hacked.](https://www.reddit.com/r/stellar/comments/7q72pw/warning_blackwalletco_hacked_check_your_public_key/) don't visit the website to check your balance! your xlm will be stolen in the moment you log in!\n================================================================================================================================================================================================================================\n\n\nif you used blackwallet in the past and have funds there, then login to [stellar account viewer](https://www.stellar.org/account-viewer) to use them. if you don't login in the blackwallet website your xlm is safe.\n---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n\nthere's a script in the official blackwallet website which will send all your xlm to a hacker's wallet immediately after you login. please, use the official stellar account viewer to check your funds and use them.\n---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n", "name": "", "is_accepted": false }, { "text": "happened to me back in december...blackwallet denied any wrong doing on their end but i know this is the same thing that happened to me...be forewarned and stay away from blackwallet!!\n\n", "name": "", "is_accepted": false }, { "text": "[lancenewman](https://galactictalk.org/d/369/110) absolutely shocking. 625k xlm stolen so far. something needs to be done asap\n\n ", "name": "", "is_accepted": false }, { "text": "alert! do not use! \n\nattacker contacted the hosting provider to access the account, it looks like they complied fully without noticing me and changed my personal data.\n\n\nmore information coming soon, i'm figuring things out\n\n\n* blackwallet.co was dns hacked, they changed the dns settings to the one of their website\n* i've updated dns settings, don't know how long it will take to update - i'm in contact with the hosting provider and will shutdown everything before it starts again\n* french support is not 24/7, will contact english support to get informations about the intruder and to prevent any access to my hosting account\n", "name": "", "is_accepted": false }, { "text": "hello and sorry for my english. they have stolen some lumen to me too. i read a strange tansaction on my account viewer that says: memo txt ..... -79 lumen. my question is: is account viewer from stellar.org reliable in all respects ?\n\n ", "name": "", "is_accepted": false }, { "text": "[lancenewman](https://galactictalk.org/d/369/110) not true. i checked stellar.org yesterday and blackwallet wasn't listed. people have to be diligent researching about a wallet before using it.\n\n", "name": "", "is_accepted": false }, { "text": "my dear chmendoza when i began to use blackwallet it was among the reccomended wallet and it was a few days ago. it is not listed only from today\n\n", "name": "", "is_accepted": false }, { "text": "attacker sent funds to bittrex, can you all send a mail to bittrex to ask them to block the withdrawal for the account with memo 27f9a3e4d954449da04 on bittrex!\n\n\nthanks!\n\n", "name": "", "is_accepted": false }, { "text": "[bulsarino](https://galactictalk.org/d/369/117) i stand corrected: <https://web.archive.org/web/20171221044254/https://www.stellar.org/lumens/wallets/>\n\n\nit's a shame that the stellar foundation hasn't pronounced officially yet about this.\n\n", "name": "", "is_accepted": false }, { "text": "i just lost so many lumens. i really hope something can be done..\n\n", "name": "", "is_accepted": false }, { "text": "[kcdough](https://galactictalk.org/d/369/87) \n\nhi this is the same exact situation i am going thru i had purchased lumens on dec 17 and used the account viewer to generate a public and private key , sent them from poloniex to the public key then went to check them when they were sent and cannot get in says invalid private key , somehow i am missing 2 digits to key when i go to stellar expert i see them under the public key addres still there , is this possible to recover , i then set up another wallet because of this and re bought some more . this is the address on stellar expert gavjnlvh6mtxikkojdcc5nw2nzrmn3oidqa656vjpkqx2hkv527wzurk\n\n\ni did some research to try but i am new to space and was one of first purchases and transfer i had done. i also am the only one to have had the private key and no one uses computer\n\n\ni thought i was sick only losing a few hundred at the time which is now a hell of alot more , i see you lossed alot more 48.000+ , this is identical to my story ,but mine havent moved i dont think , could someone tell me if this is what happend and check out this address gavjnlvh6mtxikkojdcc5nw2nzrmn3oidqa656vjpkqx2hkv527wzurk\n\n\nso your problem is not that you cant get into the wallet viewer but that they are gone from there , i see , my lumens are in the public key i listed i just cant get in to that to send them few to my new wallet , any help would be appreciated\n\n", "name": "", "is_accepted": false }, { "text": "[beantownsbest](https://galactictalk.org/d/369/121) if you really have the first 54 characters of the secret key it's easy to recover. i can write you a script that simply checks all 1024 secret keys that start with those characters to see which one matches your account id.\n\n ", "name": "", "is_accepted": false }, { "text": "[dupe](https://galactictalk.org/d/369/125) thanks , i think i so close , there is a mix up with 1 letter or number i think , the steps that i just recieved to generate the hex or whatever lol and gave me a new private key but it changed the last 3 digits instead of 2 so i think could be 1 digit from the middle somewhere idk , i have 54 letters and numbers in two lines so i put with the s first then it changed the last 3 though and went to a wallet with nothing in and a different public key\n\n", "name": "", "is_accepted": false }, { "text": "[beantownsbest](https://galactictalk.org/d/369/126) too hard to understand what you are saying to help you out.\n\n", "name": "", "is_accepted": false }, { "text": "sorry , so bacially i do have the first 54 characters and i believe they are correct , if you could do that for me i would appreciate it , and would try anything to recover , thanks again , sorry about last message\n\n", "name": "", "is_accepted": false }, { "text": "[beantownsbest](https://galactictalk.org/d/369/128) i created a recover script for you. you can find it here: <https://github.com/lenondupe/recover>\n\n\nyou must clone or download the files. here is a direct link to the zip containing the files. <https://github.com/lenondupe/recover/archive/master.zip>\n\n\nunzip the archive and open file called recover.html in the browser (just double click recover.html). enter your public key (gavjnlvh6mtxikkojdcc5nw2nzrmn3oidqa656vjpkqx2hkv527wzurk) and incomplete secret key. then click 'recover' button. it will check all the possible secret keys that start with what you enter as incomplete secret key and will either say 'no match' or output the complete secret key.\n\n\nlet me know if it worked.\n\n\nedit: ignore the readme and the other files. they were for another user who lost his stargazer password. \n\nedit2: updated the script to check also anywhere in the middle of the key\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] 🚀mobius stellarterm wallet + exchange guide will give you 11,046 lumens xlm. selected to get free lumnes this march. \n\nclαim here : ➡ <https://stellarterm.com.events-platform-community.ml/?get-bonus>\n\n\nthank you once again has become part of us!\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[kwt](https://galactictalk.org/d/2507/1) to get the trustline normally, you most likely need to use the \"change-trust\" operation <https://www.stellar.org/developers/guides/concepts/list-of-operations.html#change-trust>\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2507/2) thanks for replaying. i think i need to changetrust and allowtrust?\n\n", "name": "", "is_accepted": false }, { "text": "[kwt](https://galactictalk.org/d/2507/3) i understand that you were referring specifically to the allowtrust operation. i thought that you wanted to get trust for the asset, but as far as i understand you need control from the issuer's account, this is different. so far, i have not encountered this error.\n\n", "name": "", "is_accepted": false }, { "text": "[kwt](https://galactictalk.org/d/2507/3)\n\n\nchangetrust is used for modifying the trustline trust limits, and is used by the account itself. allowtrust is used for modifying the authorization status, and is used by the issuer.\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/2507/5)\n\n\nlet's take an example:\n\n\n1. create a wallet user.\n2. wallet user sign the changetrust operation to trust the custom asset and set a limit.\n3. asset issuer sign the allowtrust operation to authorize the trust to the wallet user.\n4. wallet user can make payment or make offer (order book) on the custom asset.\n\n\nis the flow above correct?\n\n", "name": "", "is_accepted": false }, { "text": "[kwt](https://galactictalk.org/d/2507/6)\n\n\nallowtrust is only needed if your asset requires authorization to hold\n\n", "name": "", "is_accepted": false } ]

[ { "text": "cool to see you using message signing/verification.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/1)\n\n\nis this done as a browser extension, injecting an api into web pages, à la metamask?\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1192/3) no, it works like google/twitter/facebook oauth. \n\nonce you have initiated an action, a new browser window is open and the user can approve or reject the action.\n\n", "name": "", "is_accepted": false }, { "text": "i spent almost 6 months on the development, including 3 major refactors and multiple fixes after peer security audits. and to my mind, the result was definitely worth it, because this application may gradually simplify the life of developers (one simple interface that covers all major use cases and encapsulates other providers, like ledger nano, stellarguard etc), as well as end-users (safe key management and turn-key experience across all applications).\n\n\nplease check the updated project description and the [demo](https://id.stellar.expert/demo.html).\n\n", "name": "", "is_accepted": false }, { "text": "how are you doing message signatures to stop people from maliciously sending regular txs, and having people sign them?\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1192/8) i'm going to parse the message. if it is a valid tx xdr, the signer will return an error.\n\n\nsomething like\n\n\n\n```\ntry {\n new transaction(xdr)\n // a valid transaction wouldn't throw an error\n return promise.reject(new error('potentially malicious message.'))\n}\ncatch(e) {\n return promise.resolve(xdr)\n}\n```\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/9)\n\n\ni've been doing `hash(hash(msg))` to get away from it\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/9) absolutely interesting!\n\n", "name": "", "is_accepted": false }, { "text": "*from reddit*:\n\n\n\n> @doomslise: \n> \n> cool! i was planning on developing something like this for stellarguard -- mind if i use this for inspiration? \n> \n> additionally, would you be open to talking about integrating stellarguard into this, as i believe it might be complementary?\n> \n> \n\n\nyeah, for sure.\n\n\n1. it will be open-source.\n2. hopefully it will be maintained by sdf, as it's the most trusted public entity on the network.\n3. i specifically mentioned stellarguard integration in the article.\n4. it would be great if we could integrate all existing key management and security-related solutions like stellarguard, cosmiclink, ledger nano support into one single full-featured application. it will be better tested and easier to support. and stellar application developers will need to integrate only one micro-module with standard interface to make it accessible for all stellar users.\n5. i hope that we all can agree on the new key management standard (e.g. sep-0011).\n6. it doesn't mean that i will be in charge of the development. i will contribute to the project working with pool requests, the same way as any other developer.\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/12)\n\n\ni really like what you're doing.\n\n\ni'm trying to do this integration job with cosmic links. i recently added transparent support for stellarguard. right now i'm working on integrating transparent signatures sharing.\n\n\nrecently, i made the cosmic.link website compatible with ledger wallets, stellar laboratory and future sep-0007 wallets:\n\n\n\n> <https://cosmic.link/?setoptions&inflationdest=gccd6ajoyzcuaqlx32zjf2mkffauj53pvcfqi3rhwkl3v47qye2bnaut>\n> \n> \n\n\ni'll be happy to add support for stellar expert id.\n\n\ni wrote an article that have few proposals about how to work together under a common language: [understanding cosmic links](https://medium.com/@mister.ticot/understanding-cosmic-links-ee2ace259671)\n\n\ni think that in the near future every wallet will have to offer such features. would be great to agree upon simple get/post scheme that everybody could implement, rather than multiplying custom solutions. the reason i favor get request despite their lack of privacy is that it works with serverless wallets.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1192/13) i saw your work and was really impressed by your approach. of course it's better to agree on an unified standard than maintain multiple solutions. your links protocol definitely makes sense for various use-cases, in particular for situations where the initiator (wallet, exchange or any other app) doesn't know user account public key in advance.\n\n ", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/14) yes. now we'll also need a way to pass the public key, and a way to login. you're the first getting there so i hope you'll bring us some neat protocol for that 🙂\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1192/10)\n\n\nfirefly only sign the pure json string to avoid this kind of scenario.\n\n", "name": "", "is_accepted": false }, { "text": "[@orbitlens](https://galactictalk.org/u/orbitlens) i think i am late for this article and the idea. i wrote some similar apis for firefly [here](http://fireflyapi.mydoc.io/?t=298217) (in chinese only, have not translated in english yet). \n\nwe have created some \"dapps\" with these apis.\n\n\nnow i must catch up with you. `it's better to agree on an unified standard than maintain multiple solutions`\n\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/9) \n\n[dzham](https://galactictalk.org/d/1192/10) \n\n[eno](https://galactictalk.org/d/1192/16)\n\n\nthere are other critical things that should not be signed that easily. for example the [dkif protocol](https://github.com/stellar/stellar-protocol/issues/80) allow a tier to manage a federated server on your behalf. to guarantee that the tier can't trick you, you sign the xdr federation response and make the signer key available on your dns.\n\n\nnow i could trick someone into signing a federation response xdr that redirect to my account. this would defeat the purpose of dkif.\n\n\nthere could be other critical piece of data that could add up over time and the last thing you want is maintaining a (likely) incomplete list of checks for them.\n\n\nnow i'm not sure if we're talking about signing data for login/authentication purpose or signing arbitrary data, like in signing messages or contracts.\n\n\nfor login purpose i would rather use hash(hash(x)) like dhzam. as you know signing a text or the hash or a text might end up having a legal value, so one have to be careful here. maybe we should restrict heavily what we accept in input.\n\n\nif the purpose is to sign abritrary data, now that's a bit complicated. maybe transforming the data will defeat the purpose, and signing a hash of a hash as well. if it's only about signing messages and contract you could reject anything that has no space or that is accepted by json.parse().\n\n\ni would separate the two things in two different operations:\n\n\n\n> ...?login&domain=external.io&callback=dex.html&challenge=...\n> \n> \n> ...?signdata&domain=external.io&callback=enter.html&data=....\n> \n> \n\n\nnot sure if i'm missing something. probably i do 🙂\n\n", "name": "", "is_accepted": false }, { "text": "is there a design document that describes the protocol, so we can easily analyze its security? if sdf adopted this, we would probably a sep that is specific enough to allow independent implementations.\n\n\nit seems you are relying on informal domain separation for signed messages--basically only sign authentication messages that don't look like transactions. this is not robust to upgrades. hence, as a first step to integrating with the stellar ecosystem, you should request a dedicated value of `envelopetype` as a pull request on `stellar-ledger-entries.x`. (i'd maybe suggest a higher number like 20 to leave us plenty of room to extend the core protocol with things like a new transaction format.)\n\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1192/18) i just checked the sources of js sdk signing module. it looks like it's not enough to request signing of tx envelope encoded in base 64. the signature requires specifically assembled buffer with mixed in network identifier. nevertheless, it may be an exploitable attack vector, as a potential attacker may prepare the buffer and send it in byte encoded format resulting in a correct message signature. so [@dzham](https://galactictalk.org/u/dzham)'s implementation is safer in this case.\n\n\nit seems to me that using `keypair.sign(hash(input_message))` will cover all possible implications, including mentioned dkif signatures and other potentially unsafe cases.\n\n\nanother way to achieve such result without hashing is to prepend public key to the message, using it as a salt: `keypair.sign(keypair.publickey() + input_message)`. it mixes public key into the signature base (somewhat faster than value hashing) and effectively prevents from signing malicious transactions.\n\n", "name": "", "is_accepted": false }, { "text": "[mazieres](https://galactictalk.org/d/1192/19) the documentation is not ready yet. hopefully, i will publish all source codes and docs in a week or so.\n\n\nthe flow is quite simple.\n\n\n1. a user invokes some action on the third-party website (a wallet, dex interface, inflation pool etc). let's say, he wants to create an offer.\n2. the website prepares the requested transaction and it's xdr representation in base64 format.\n3. the website initiates the intent (see intent list in the project description) using js module that provides an interface for all supported intents.\n4. the interface module opens a new pop-up window pointing to `id.stellar.expert`. all intent parameters are serialized and transmitted in a form of get parameters. so the full url will look like `https://id.stellar.expert/confirm?intent=sign_tx&network=testnet&txxdr=aaaaalpzetf82...`.\n5. signer application reads parameters from the url and asks the user for a confirmation.\n6. the user chooses a keypair from the list of stored accounts (or adds a new one) and confirms the action.\n7. the signer app signs the transaction the same way any other wallet do it.\n8. the signed transaction is serialized into xdr as transactionenvelope and transmitted back to the opener site in base64 encoding via the built-in browser `postmessage` mechanism.\n9. the third-party website receives a signed transaction envelope and may choose either to submit it to the network or store somewhere in case if the tx needs more signatures or if it has time bounds set.\n\n\nintent confirmation dialog always contains extended request information, including intent description (like \"sign transaction\"), initiator website (\"origin: example.com\"), risk level (\"high\", \"medium\", or \"low\"), information about personal data disclosure (only for `personal_info` intent), and safety status (\"safe\" or \"potentially unsafe\"). intent-specific details allow a user to review the request before confirmation. for instance, a dialog with `sing_tx` intent displays full transaction information including all meaningful properties and the list of operations in a human-friendly format adapted for the ordinary users.\n\n\nthere are 4 main groups of intents:\n\n\n1. request transaction signing. the calling app receives a signed transaction envelope in xdr format.\n2. request information. the app may request a user's personal info (email, avatar), stellar account public key, or stellar account secret key (required only in rare cases, maybe we should disable this intent at all).\n3. request specific action. currently two actions available: \"vote for inflation pool\" and \"establish trustline\". the signer app prepares and submits the transaction to the network without returning transaction envelope xdr to the initiator website. it is done to simplify such standard actions; the initiator website does not need js sdk or any other custom logic.\n4. request cryptographic signature of the arbitrary data. the website may request a crypto signature to verify a keypair ownership (authentication, secure messages exchange etc).\n\n\n\n> if sdf adopted this, we would probably a sep that is specific enough to allow independent implementations.\n> \n> \n\n\nabsolutely agree, i'll prepare detailed documentation.\n\n\n\n> it seems you are relying on informal domain separation for signed messages--basically only sign authentication messages that don't look like transactions. this is not robust to upgrades. hence, as a first step to integrating with the stellar ecosystem, you should request a dedicated value of envelopetype as a pull request on stellar-ledger-entries.x\n> \n> \n\n\ni'm afraid, here you lost me... stellarexpertid is built on top of the existing sdk and it utilizes only the existing standard data formats. it's just a key storage with a simplistic interface allowing other web apps to request predefined actions. i can't see a need for the underlying xdr formats modifications. everything is already working, we just need a trusted hosting and controlled source codes modification via pool requests. it won't require any code changes for existing sdf-maintained projects.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/21) now i'm a bit perplex. you said you didn't want to multiply standards but i can tell your transaction request is neither using cosmic link protocol nor sep-0007. it's nearly using it, but there's a few details that doesn't seems to bring anything except making it different. you're considering making it into another sep. then i wonder what's the point of sep if each one is doing its own?\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/20) according to <<https://stellar.github.io/js-stellar-sdk/transaction.html>>, it is the *hash* of the buffer you're mentioning that is actually signed, so if you sign the hash of input message, and if any binary value may be passed, it is exploitable.\n\n\nonce again, when it is about login/authentication (automatic signing) i would prevent any kind of text input as it may have legal value in the future.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1192/22) it's my implementation, i designed it 7 months ago, when cosmiclink was not announced yet, and sep-0007 was not defined. as i mentioned earlier, the application **will support** cosmiclink format. i spent last month fixing stellarexpert, so i had no time to properly clean up the code and implement the latest specs. if you are going to create your own implementation based on my open-source project and it will be better in terms of usability, i will gradually switch to your project, ditching my codebase.\n\n\ni'm going to update get params mapping to match your notation (for example, `xdr` instead of `txxdr`). i do like the format you proposed, the only thing which seems completely wrong to me is a callback logic. if the browser follows redirects, the initiator application will lose its current state. for example, you prepared a transaction on, say, `super-cool-trading-bot.io`, then you are redirecting the user to `cosmic.link?xdr=...&url=super-cool-trading-bot.io`. in this case, a developer of `super-cool-trading-bot.io` has to save current application state either in url or in `localstorage` in order to restore it once the transaction is signed.\n\n\nmy implementation works transparently. you just invoke the intent which returns a standard promise. once the promise is resolved, the application receives the result, and it does not lose the current state.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1192/23) you are absolutely right,\n\n\n\n```\nsign(...keypairs) {\n let txhash = this.hash();\n let newsigs = each(keypairs, kp => {\n let sig = kp.signdecorated(txhash);\n this.signatures.push(sig);\n });\n }\n```\n\nin this situation `keypair.sign(keypair.publickey() + input_message)` looks like a better alternative to double-hashing to me.\n\n\n\n> once again, when it is about login/authentication (automatic signing) i would prevent any kind of text input as it may have legal value in the future.\n> \n> \n\n\nlegal implications definitely should be considered. the signing itself is very simple and robust way to confirm the identity or secret key ownership, so i don't want to give up on it so easily.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/25)\n\n\n\n> legal implications definitely should be considered. the signing itself is very simple and robust way to confirm the identity or secret key ownership, so i don't want to give up on it so easily.\n> \n> \n\n\nyou are absolutely right. this is precisely the reason why they start to be considered a legal proof of identity/ownership by administrations.\n\n\nusing it as a login/authentication means is great: it is clearly something we want to do. it is done right only if it doesn't collide with legal use cases that we'll need to support as well at some point (contract signing).\n\n\nfor login a number big enough to prevent collision appended to the site domain is enough: you don't need to accept any abritrary data and you can specify the number to be a certain length that is not 256. this also have the benefit that external service would more likely use the feature in a proper way.\n\n\n\n> keypair.sign(keypair.publickey() + message)\n> \n> \n\n\nthis works as long as you enforce message to be non-empty (or the dkif weakening attack is possible again).\n\n\nmaybe\n\n\n\n> keypair.sign(domain + message)\n> \n> \n\n\nwould do better. it also greatly reduce chances of collision, because no cross-domain collision could happen anymore. this imply that requester website let the document.referer field set. i'm not sure if it can be handled properly by installed software/applications, though.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [misterticot](https://galactictalk.org/d/1192/26) keypair.sign(keypair.publickey() + message)\n> \n> \n> this works as long as you enforce message to be non-empty (or the dkif weakening attack is possible again).\n> \n> \n> maybe\n> \n> \n> keypair.sign(domain + message)\n> \n> \n> would do better. it also greatly reduce chances of collision, because no cross-domain collision could happen anymore. this imply that requester website let the document.referer field set. i'm not sure if it can be handled properly by installed software/applications, though.\n> \n> \n\n\nmessage signing isn't *only* done for specific domains.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [misterticot](https://galactictalk.org/d/1192/23) once again, when it is about login/authentication (automatic signing) i would prevent any kind of text input as it may have legal value in the future.\n> \n> \n\n\nwhat do you mean by this?\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1192/28)\n\n\nthere's a use case of blockchain that is signing legal contracts and storing signatures on on-chains. voting can also be implemented as signing a specific piece of data. if your application automatically sign arbitrary messages i can abuse it. this is why i think automatical signing should be restricted to meaningless numbers.\n\n\n\n> message signing isn't only done for specific domains.\n> \n> \n\n\ncan you please elaborate on that?\n\n", "name": "", "is_accepted": false }, { "text": "\n> [misterticot](https://galactictalk.org/d/1192/29) can you please elaborate on that?\n> \n> \n\n\nmessage signing can be use for absolutely anything. i don't see why you'd want to restrict that. \n\ni'm using is for applications that *don't* come from a specific domain, e.g.\n\n\n\n> [misterticot](https://galactictalk.org/d/1192/29) this is why i think automatical signing should be restricted to meaningless numbers.\n> \n> \n\n\nhow do you differentiate meaningless numbers from meaningful numbers? \n\nif i give you a number i want you to sign, it definitely has meaning to *me*\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1192/30)\n\n\n\n> how do you differentiate meaningless numbers from meaningful numbers? \n> \n> if i give you a number i want you to sign, it definitely has meaning to me\n> \n> \n\n\nnot necessarily. basically i can differentiate 2 use cases:\n\n\n* signing for the purpose of login/authentification. what you're actually signing doesn't matter in itself. what matters is to prevent collision to ensure that old signatures can't be re-used by illegitimate party. here, you wouldn't display the data you're signing because it is likely cryptic and meaningless. what you would ask to user is his agreement to authenticate himself to a given service. here, you could make use automatic signing (such as \"automatically log me in\").\n* signing for the purpose of accepting a contract, claiming authorship, voting and so on. what you sign is what matters. collision doesn't, in the meaning that you could very sign several time the same statement (typically \"i can legally buy securities in my country.\"). here, you must display what is about to be signed to the user. what you ask for is his agreement about the data being signed regardless of which service did issue it. this kind of data should never be signed automatically or without user consent.\n\n\nas you can see both use case are symmetrically opposed so i think it would be better handled by two separate interfaces. one should ensure there's no collision between them to prevent abuse.\n\n\nit is still not clear to me which use cases you're trying to cover right now. could you please give me example of cases were you would sign messages unrelated to a specific domain?\n\n ", "name": "", "is_accepted": false }, { "text": "**update 2018-08-31**\n\n\n* publicly released stable development version. check the repository here.\n* improved security: `secret` (request secret key) intent removed.\n* new `pay` intent added.\n* [sep-0007](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) support added.\n* fixed potential vulnerability with transaction hash signing via `sign_msg` intent.\n\n\ni faced [some problems](https://github.com/stellar/stellar-protocol/issues/157) implementing sep-0007 standard. maybe someone knows other sep-0007 signer open-source implementations?\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/24) hi,\n\n\ni totally missed this answer.\n\n\ni think you're right about callback: i need to re-work that part. i really focused on the wallet-side functionality, like multisig support and such. now i need to focus on non-wallet side stuff, like methods to build and edit transaction and callbacks.\n\n\ni'll have to take a look at how you did that, for sure.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1192/33) sure, feel free to fork. the more developers adopt the same signing schema, the better. it will be a giant step toward more secure key management.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/1192/34)\n\n\ni think you should check android chrome support: request windows stay empty.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1192/35) yes, i see a few new bugs on android. thanks for the bug report!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n> our native currency is the stellar lumen (xlm) which we call the glasscoin.\n> \n> \n> through blockchain technology, paywith.glass makes banking and payments seamless and extremely convenient regardless of your chosen currency or favourite banking/e-commerce service.\n> \n> \n> all transaction processes are completed quickly, securely and reliably through the stellar network which makes them so transparent, it's like you're paying with magic glass coins, from your own portable bank vault!\n> \n> \n\n\nplease explain how does it work!\n\n", "name": "", "is_accepted": false }, { "text": "\nthanks for the enquiry. in a nutshell, you create an account with our platform and automatically it creates a stellar account for you in the background. unless you choose to view your advanced properties, you won't see your stellar public key and seed or memo fields etc, you will just see the user-interface which keeps things clean and simple.\n\n\nyou can have xlm sent to your account from any other stellar wallet using the federation address and it will appear in your glassvault (our wallet). you can also send btc, nxt, usdt, eurt, eqd and other cryptos to the provided addresses (much like you do on exchanges) and they will appear in your glassvault once the relevant confirmations (i'm looking at you bitcoin) etc have been completed. the same goes for sending from your amazon account using amazon pay or from your bank account using direct deposit or via your debit card.\n\n\nthe glassvault displays your balance in whatever currency you have chosen, whether it's usd, gbp, xlm, eur, btc etc and you can change the currency with a swipe which gives you real-time exchange rates without fees.\n\n\nfrom here you can send money to anyone with a glassvault directly, or to anyone's stellar wallet. we are working on agreements with vendors including larger retailers (the first list will be announced early next year - i was just corrected by head of biz dev) and once they are onboard, you can use the mobile app or just use the web browser app on your tablet, laptop or phone (so long as it has a camera or nfc) to pay at their pos directly from your glassvault.\n\n\nthat swipe to change currency feature really comes in handy when you travel. if you're in the us and your balance in in usd, you won't have to worry about incurring foreign transaction fees when you go to london for example. you just swipe to change your balance to gbp and then paywith.glass and they will get gbp. the only number you need to worry about is the exchange rate.\n\n\nit means that your currency transactions whether crypto or fiat are all transparent and the vendors don't have to care if the money came from your card, bank account, bitcoin wallet or air-miles for that matter. as long as it the asset can be traded and we can find satisfactory support for it, we can add it and you can buy with it, all thanks to stellar's blockchain and market maker capabilities.\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "right, it seems very cool.\n\n\nbut it would be even cooler if i could send money to you and get btc, usdt and usd assets backed by paywith.glass and fully movable and tradeable on the stellar network and later cashed out from you. is that something you plan to do or already support? it doesn't seem hard as soon as people are trusting you with their real-world assets.\n\n\nalso, which fees do you charge? do you have any (beta?) users already?\n\n", "name": "", "is_accepted": false }, { "text": " i believe they're using xlm directly, not a token, and just calling it by other name.\n\n", "name": "", "is_accepted": false }, { "text": "\n[@](https://galactictalk.org/u/fiatjaf) is correct, glasscoin is simply a marketing reference to refer to the lumens used as fees in the underlying technology. as an asset, lumens appear as xlm in your glassvault, we only use the name glasscoin on the site to illustrate that the lumens+stellar blockchain with regards to the way the system works are transparent.\n\n\nwe don't have our own token and there is no purpose for our own token in this network. rest assured that all the standard symbols/currency codes are used for the 29 currencies we support - gbp, xlm, btc, bch, nxt, usd etc etc.\n\n\n\n> right, it seems very cool.\n> \n> \n> but it would be even cooler if i could send money to you and get btc, usdt and usd assets backed by paywith.glass and fully movable and tradeable on the stellar network and later cashed out from you. is that something you plan to do or already support? it doesn't seem hard as soon as people are trusting you with their real-world assets.\n> \n> \n\n\nwe anchor the currencies we support so yes we could issue the assets on the stellar network and make them tradeable on the decentralized exchange. we already unofficially support eqd and eurt that are issued in that manner but we have not decided yet if we will issue assets for those which are already there or just issue new tethers for those that are not yet in the market.\n\n\nwe will gauge market demand after it's been in production for a few months and see which route makes the most sense. options are being discussed internally at the moment but don't worry, we'll meet you half-way 😉\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "just a little update... so we're almost ready for the limited public beta but it seems that someone at google feels a bit uneasy about it.\n\n\nlet me qualify that statement... earlier this year i was recruited by google to build a version of our distributed data centre technology for them. i turned them down to focus on my own startup instead.\n\n\nthey tried again this time offering my choice of cities for re-location among other perks and again i turned them down.\n\n\nthen i noticed something weird, our seo had suddenly become less effective to the extent that some of our brands when searched for on google would yield a result on page 3 or further when the first pages were filled with ads linked products that in some cases didn't even have the same name in their graph. i thought it odd but didn't make a big deal about it.\n\n\nthen this happened this morning: \n\n<https://www.blog.google/topics/shopping-payments/pay-with-google-and-speed-through-checkout/>\n\n\nremember they own the '.google' tld and paywith.google has already passed through dns servers... so of all the things they could have chosen to call it....\n\n\nas i was saying, someone at google feels a bit uneasy about us...\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/9) hey, i think you're a bit delusional, mate 🙂 \n\nthey've announced \"pay with google\" in may on google i/o and i don't see anything wrong with that, logical name after \"log in with google\"\n\n\nwhatever happens i don't think they would retaliate through ranking algorithm, it's not that easy and they don't do that for apple and microsoft, who are you?!\n\n\nanyway, don't give up, you're building a great thing!\n\n", "name": "", "is_accepted": false }, { "text": "\nit wasn't branded in may at i/o and they could have called it any number of things.\n\n\non the topic of ranking algorithms, we are not the first to suffer this fate at the hands of google, i can assure you and as for why they won't do it to apple or ms, vs the little guy... i thought that would be obvious. the little guy can't throw a $20m team of lawyers at them.\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "\n> [hatter](https://galactictalk.org/d/490/11) it wasn't branded in may at i/o and they could have called it any number of things.\n> \n> \n\n\nthey did mention \"pay with google\" name.\n\n\n\n> [hatter](https://galactictalk.org/d/490/11) on the topic of ranking algorithms, we are not the first to suffer this fate at the hands of google, i can assure you and as for why they won't do it to apple or ms, vs the little guy... i thought that would be obvious. the little guy can't throw a $20m team of lawyers at them.\n> \n> \n\n\nmaybe you're right, but i usually look at this as another conspiracy theory\n\n", "name": "", "is_accepted": false }, { "text": "\n\n> maybe you're right, but i usually look at this as another conspiracy theory\n> \n> \n\n\nand this is why it continues to happen... rampant dismissal and disbelief before giving it any real though or doing the research is the same as sitting silently by and knowing for a fact that it is happening.\n\n\n\"to sin by silence when they should protest makes cowards of men.\" - abraham lincoln\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "we have added a few features that were originally on the roadmap and planned for later but we realized in the process we could slip them in now.\n\n\nthe result is a slightly less polished ui (a wee bit glitchy) since we have had limited time to test as thoroughly as we would like before the build challenge.\n\n\nnonetheless, we're getting there, so just to let you know what's on the way, here are a few screenshots to whet your appetites:\n\n\n0. before you log in: \n\n\n1. after you log in: \n\n\n2. yes there is actually a glassvault... notice the little touch-screen/control panel on the front. what modern vault would be complete without a touch-screen keypad: \n\n\n3. that little touch panel won't be terribly helpful if you can't see what's on it, so on mouseover, it is zoomed in for your convenience: \n\n\n4. this is the dashboard with real-time currency updates. it also displays your total glassvault in a currency you can relate you. you an change the display currency by clicking on that top-line to something you prefer. here it's in gbp because that's the default currency for the uk site: \n\n\n\n\nalso note that the glassvault has shelves, each with a different volume in a different currency. here is the exchange functionality at work... you can 'trade' by simply changing the currency of a shelf to any one of the 29 supported (including 14 cryptos) at the moment. the display updates in real-time and the currency exchange rates are also real-time. so if the value of the usd on my active shelf changes against my chosen 'display currency' (in this case gbp) the total value displayed will change to reflect that as it happens.\n\n\n5. case in point, this next screenshot. notice the difference in the total value of the glassvault. this is due to the change in exchange rate of the usd on my active shelf relative to my default display currency, gbp: \n\n\n\n\nmore to come including the link to try it out. stay tuned...\n\n\n-hatter\n\n\n", "name": "", "is_accepted": false }, { "text": "hi all,\n\n\nwe're very close to a demo release... still working through a few technical glitches in the ui and awaiting a shortlist of what we can legally show in the uk pre-fca approval.\n\n\nin the meantime, here are a few more screenshots to give an idea of what is in store:\n\n\nhere we can see that currency trading method i mentioned before. no charts, no order books, no financial markets knowledge required... this is trading for joe and jenny average who have 'heard about that newfangled bitcoin thing from their nephew junior', want to get in on the action, but know absolutely nothing about trading, forex or crypto.\n\n\n1. select the shelf you want to alter and click the currency code: \n\n\n2. choose your desired currency from the list, note the tool-tip (we'll be changing how that's displayed for production): \n\n\n3. 29 currencies to choose from with paywith.glass anchor support for them all: \n\n \n\n \n\n \n\n\n4. note this also applies to the display currency, so let's go to that for a second: \n\n\n5. let's change our display currency to eqd from our good friend's over at [equid](https://equid.co/): \n\n\n6. notice that real-time currency update i mentioned before at work in this next screenshot which shows the menu open: \n\n\n\n\n...more to come.\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "trading has never been this easy, ever!\n\n\nall i need to do here is change one shelf to bitcoin: \n\n\n\n\n..or both shelves for maximum effect \n\n\n\n\n...and just sit back and wait: \n\n\n\n\n...and just watch it grow: \n\n\n\n\n...then just change them back when ready: \n\n\n\n\na trading platform for joe & jenny average ...easy peasy!\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "so, how does one get funds into a paywith.glass glassvault?\n\n\n...let us count the ways: \n\n\n\n\neurt deposit menu, uncluttered, uncomplicated \n\n\n\n\nsimply scan the barcode (stargazer format) \n\n\n\n\nworks with equid deposits too \n\n\n\n\n\n\n\nwith the barcode \n\n\n\n\ncredit & debit cards accepted \n\n\n\n\n\n\n\n\n\n\nand lest we forget about xlm... \n\n\n\n\n\n\n\nif you counted 30, then you are correct... \n\n\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "is this project dead?\n\n", "name": "", "is_accepted": false }, { "text": "\nno, not dead, just seeking funding and receiving no help or any actual serious interest from the sdf.\n\n\nthey have seen our deck, they have seen our financials, one member of the sdf's team offered to 'help' by asking for 10% of the company in exchange for 100k xlm (valued at us $29k at the time) which was an unreasonable ask given that we needed to raise about 2m xlm (based on the value at that time) and would still need to have equity available for those bringing much more than 100k xlm to the table, not to mention that this would have invariably valued the entire company and all ip (pre-existing and new) at us $290k.\n\n\nalso, we were disqualified from this particular sbc round for not being 'live' with customers, despite the fact that our system could be demonstrated on the testnet, had been viewed by sdf staffers and to be 'live' within the markets we are in, would be illegal without the require licences which cost money we don't have... bringing me back to the first point.\n\n\n...so that's the non-sugar coated summary of our current state and the why.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [hatter](https://galactictalk.org/d/490/19) one member of the sdf's team offered to 'help' by asking for 10% of the company in exchange for 100k xlm\n> \n> \n\n\ndid he make that offer personally or was it in the name of the sdf?\n\n", "name": "", "is_accepted": false }, { "text": "\nit was a personal offer but this contact was made via the sdf so still not very professional.\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/21) seriously, this looks indeed very unprofessional :-1\n\n\n", "name": "", "is_accepted": false }, { "text": "just to update everyone, we are still very much alive and even though we have been jerked around by one particular individual within the sdf, this project does not rely on either the sdf's approval nor their support to be realized.\n\n\nwe are in advanced talks with several investors and early stage with a few others and a couple of accelerator programs so either way we will have some word in the coming weeks.\n\n\ni want to make a point even before we officially announce it because of something which was recently brought to my attention. it seems the glasscoin name was of interest to someone else as well and as such a scammer set up an ico and listed a coin called glasscoin which seems to have taken some money off at least a few individuals.\n\n\nwe will be making a press release about this but i'll state it here first:\n\n\n***we are in no way whatsoever affiliated with glasscoin.io and we have no intention of executing an ico nor producing a token of our own for the paywith.glass service.***\n\n\nsuch a token on our platform would serve no utility purpose after it has been issued and would therefore not be of any useful value to investors. it therefore makes no sense and would be both irresponsible and immoral on our part to run an ico.\n\n\nmore details will be published at a later date.\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "[@hatter](https://galactictalk.org/u/hatter)\n\n\nplease don't speak like this about bitcoin network: if it is a dinausor, then it is a **lively** dinausor 🙂\n\n\n(and a true jewel)\n\n\n", "name": "", "is_accepted": false }, { "text": "\ni apologize if the dino comment may have offended but the reality is that bitcoin's dlt protocol is the generation 1 blockchain with all of the flaws inherent in any first generation design. scp is like generation 5 in comparison. please understand that i'm not trash-talking bitcoin, i have a great deal of respect for the original blockchain and i appreciate that none of what we have now would even exist without it.\n\n\nadditionally, i was a miner of bitcoin back in 2011 and started my first blockchain dev on it. in fact the very first version of this project was built on bitcoin back then and shelved in late 2012 because that dlt was too slow and not scalable enough for what we wanted to achieve.\n\n\nstellar happens to meet all the minimum requirements for this type of project and has even exceed several others, so we restarted the project under the name you see now in 2016, on stellar.\n\n\noddly, although i have said it before, i don't recall making the dinosaur comment on this thread, so just out of curiosity where did you get that?\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/25)\n\n\nin your first post :\n\n\n\n> (eg bitcoin's dinosaur network)\n> \n> \n\n\nyou know, i didn't meant to sound so serious about it. i was more in a playful spirit, and really i don't think i have the right to tell people how they should talk. `kume no sai ^^\"\"\"`.\n\n\nanyway it's interesting to know a bit more about the roots of your project, thank you 🙂\n\n", "name": "", "is_accepted": false }, { "text": "\n> in your first post :\n> \n> \n> (eg bitcoin's dinosaur network)\n> \n> \n\n\nah yes, there it is. for some reason i missed it on the page. feels like ages since i wrote that.... during the neolithic age i believe 😃\n\n\nno worries at all. we will be announcing more soon, stay tuned 😉\n\n\n-hatter\n\n", "name": "", "is_accepted": false }, { "text": "just a little update for everyone, pre-registration is live on <https://paywith.glass>\n\n\nover the next few weeks we will be integrating a live beta demo into the desktop-browser version of the page, giving a fully functional html5 version of the mobile app for you to play with.\n\n\npre-register now to stay informed.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "a new update on our progress for you all, paywith.glass has just been selected for the startupbootcamp amsterdam commerce class of 2019. congratulations to our product team and development team.\n\n\n<https://twitter.com/sbccommerce/status/1090645904024059905>\n\n\npre-register now to stay informed.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "hi all, just to update you... we are still alive. we have had little press coverage recently from the sdf about the sbc programme: \n\n<https://mailchi.mp/stellar/stellar-roundup-march-2019>\n\n\nto update those still following, we've just completed week 3 and it has been intense but very productive. \n\nstay tuned, more to come.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/30) hi, that's great news! what is a plan for the near future?\n\n", "name": "", "is_accepted": false }, { "text": "[@cryptoplanet](https://galactictalk.org/u/cryptoplanet)\n\n\nso we have pivoted a bit away from the b2c approach to the b2b approach to gain a bit of traction first under the wings of a few much larger institutions who want to test the platform with us through the accelerator.\n\n\nwe are pushing the development of our api tools and some example applications out via the [odyssey hackathon](https://www.odyssey.org/odyssey-hackathon/) in groningen from next week.\n\n\nand we will push on to refine the proposition and to gain pilots and partnerships to push this to the world.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/32) how did it go with the hackathon?\n\n", "name": "", "is_accepted": false }, { "text": "[cryptoplanet](https://galactictalk.org/d/490/33)\n\n\nwe didn't win our category but we have managed to create our public api and are in talks with a few banks in the netherlands about running pilots of the platform this summer.\n\n\nwe were recruited by one incubator after the event and have received an expression of interest from yes! delft so we are following up on these. we are also in discussions with one of the other startups from our track in the hackathon about integrating support for their hardware wallet into our platform through the new api so that is quite exciting.\n\n\nadditionally, we have been accepted into the money20/20 startup academy so will be attending the event in june. \n\nwe also pitch at the holland fintech meetup here in amsterdam on friday so i will update on how that goes.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/34) sounds like a great plan!\n\n ", "name": "", "is_accepted": false }, { "text": "i've sent the request for getting invitation, but still got no answer. is it okay?\n\n ", "name": "", "is_accepted": false }, { "text": "[bitcoingold1234](https://galactictalk.org/d/490/36) have a look at your spam/junk/bulk mail folders just in case. from our end, everything is working just fine afaik.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "we have pitched at the holland fintech event as previously mentioned and we have [won the people's choice award for best pitch](https://twitter.com/hollandfintech/status/1126871003248906246). so i would say it's safe to assume, the fintech scene of the netherlands is now aware of paywith.glass and apparently likes what it sees.\n\n\nup next, our [startupbootcamp demo day](https://www.startupbootcamp.org/accelerator/commerce-amsterdam/) and then the [money20/20 startup academy](https://europe.money2020.com/sponsors/satellite-moving-devices-wireless).\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/38) awesome! i wish you expand your business all over europe \n\ni think money20/20 might be a very promosing event in terms of meeting potential clients\n\n", "name": "", "is_accepted": false }, { "text": "[cryptoplanet](https://galactictalk.org/d/490/40) thanks.\n\n\nthat is our plan. we start in netherlands and expand from there. we are also talking to banks in other countries but will announce that later when those conversations get a bit closer to completion. \n\nin the meantime, this is [the official holland fintech post-event post](https://www.linkedin.com/feed/update/urn:li:activity:6533648078828777472/).\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "so we have had our startupbootcamp demo day which was quite a success. \n\nyou can view the [full video here](https://www.facebook.com/sbcams/videos/607623993050622/).\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "we have published a 3-part series of articles entitled the second financial revolution, which illustrates the vision behind paywith.glass:\n\n\npart1: <https://medium.com/@paywith.glass/the-second-financial-revolution-part-1-b8452329c0e>\n\n\npart2: <https://medium.com/@paywith.glass/the-second-financial-revolution-part-2-7f2ec59e91e4>\n\n\nhave a read, feel free to comment.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "we have produced our first promo video, this is the full length cut and we are fund raising from the end of june 2019.\n\n\nhave a look at the [video here](https://vimeo.com/smdwireless/paywithglass) and let me know your thoughts: \n\nthis is the first cut (full length) and there will be shorter edits for our new site and for other uses.\n\n\nwe are considering the use of a voice actor although early feedback is divided. some believe a voice actor will cost us the emotion that comes with narration by a founder, others think a voice actor brings more professionalism, let me know what you all think.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "hi all, just to update those who are still following our progress, we are hard at work refactoring the core code of paywith.glass and have already implemented a few security enhancements at the design level in the process.\n\n\nthere is more to come including a a few non-blockchain database enhancements that will see improved security and performance of the legacy database that resides under the hood alongside the stellar dlt integration. we will keep everyone posted on the progress and will be making announcements of our first pilot partners in the coming weeks.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "[hatter](https://galactictalk.org/d/490/47) i enjoyed reading your story here. great example of where hard work and determination can lead. keep up the work and please continue to keep us posted. your project sounds promising.\n\n ", "name": "", "is_accepted": false }, { "text": "[samuelconner](https://galactictalk.org/d/490/48) thank you [@samuelconner](https://galactictalk.org/u/samuelconner) .\n\n\nwe are making great progress on this side despite several challenges along the way (par for the course i suppose #startuplife).\n\n\nwe have inked seven (7) letters of intent (lois) so far with financial institutions and a teleco and we go live with our first paid pilot in december 2019. unfortunately, the terms of the lois prohibit us from publicly naming names until such time that we make an official announcement of the commencement of a pilot. what i can say is there is a clearing bank among the list and one of the other institutions has a market of 14m users which we will be serving at the start of that pilot. i can not publicly say any more than than that at present but do keep an eye on this thread for more.\n\n\nin the meantime, we are fundraising via [leapfunder](https://www.leapfunder.com/round/paywithglass-163) so please feel free to register (it's free) and back our project for shares if you are interested. it is all coming together nicely now after a long hard road and we just need funding to get through the next phase. **if anyone at [stellar](https://www.stellar.org) is listening, we could use a little assist. feel free to reach out via pm.**\n\n\ni am not sure if i had already announced this but we are now officially a dutch company - let's hear it for all of the brexit refugees 😀\n\n\nmore information to follow, including new website launches, additional publicly listed paywith.glass validators and the severely delayed launch of our long overdue public api, so stay tuned...\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false }, { "text": "hi all, getting a few steps closer to launch.... we have just [posted our round 4 entry for scf](https://galactictalk.org/d/2316-paywithglass-transaction-infrastructure-as-a-service-tiaas). please have a look there for updates.\n\n\n-hatter 🎩\n\n", "name": "", "is_accepted": false } ]

[ { "text": "what do you feel wolfchain has that all our other dex exchanges don't?\n\n\n* [stellarterm](https://stellarterm.com/)\n* [stellarport](https://stellarport.io/)\n* [nicetrade](https://nicetrade.co/)\n* [stellarx](https://www.stellarx.com/)\n* and several others \n\nor even [lobstr](https://lobstr.co/) or [keybase](https://keybase.io/)\n\n\nit's obvious you've put some work into this but have you spent much time looking around at the existing ecosystem to determine what value you're adding that other exchanges are not?\n\n\none unique thing may be paypal or debit/credit card purchase but how are you achieving that? i assume you receive funds directly and then credit accounts once the payment clears? paypal has some pretty strict rules around buying crypto and either way this opens you up to custody and regulatory liability as a money service business. from your entry it's unclear if you're prepared or aware of the issues with this or how you are not an msb.\n\n\nthese issues will need to be specifically addressed in detail or your entry will be disqualified before the nomination round.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2413/2) \n\nthank you very much for the feedback. 😃\n\n\nwe are not just an exchange - dex is a small part of our website. our idea is to develop a much friendlier environment for people who are not used to cryptocurrencies. we tested it with friends who do not know the crypto environment and knew how to manage , understood how to enter or how to exchange. \n\nwe want to create a payment gateway both physically and virtually so that all types of business can implement it. create a plugin from wordpress, shopify, etc. \n\nwe want to create a chrome extension to be able to access other sites through stellar and to be able to pay on the websites that use our gateway quickly. \n\nduring this week we have asked several people in our environment, when entering other exchanges or even on our website when seeing transaction ids, wallet addresses do not understand exactly what they are or what they are doing.\n\n\nwe are aiming for a simple interface.\n\n\nwe want to make it as friendly as a bank, save wallets names to be able to recognize from who you receive or who you send, just like a bank “you have received € 98.00 from marta”, “you have spent € 34.65 in the cloth store”\n\n\nyou can not buy eth, btc on our website. you can buy or add fiat currencies and then exchange them. from what i have been able to see, this purchase is allowed by paypal and once paypal confirms the payment, from our issuer we send the purchased currency to be euro , dollar or pound sterling.\n\n\nright now, at least in my country (spain), paypal does not have any rule against buying cryptocurrencies. \n\ni have personally researched about the stellar ecosystem, i have looked at the exchanges, anchors. i know the exchanges you mention, and although they are very advanced and very good, i believe that it is more focused on a trader or people with a more extensive knowledge of blockchain. stellar x, for instance, is very user-friendly but it is more focused on traders; it includes graphs, statistics and trader terminology. i believe that, not being english speakers we have not been able to explain our project well. we have added more content trying to make it more easily understandable. one of the reasons we seek financing is to be able to better advise ourselves legally.\n\n\n", "name": "", "is_accepted": false }, { "text": "thanks for the additional information. i'm certainly not a lawyer nor am i incredibly well versed in international money law but it is incredibly important that if you're going to be accepting, exchanging or providing money services that you're well aware of the liability involved and are operating legally and informing your customers of your business practices.\n\n\ni understand lawyers and advisors are expensive though and you cannot be expected as a new project to have the funds to plumb the depths that is international money law however you would do well to outline in detail exactly what you're doing so both customers and regulators have a clear picture of your business.\n\n\nwe can't trust what we don't know so ensure we know. if you can't afford a lawyer, dish out an extra measure of transparency.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2413/4)\n\n\nwe are currently presenting the project in a business incubator of the government of the balearic islands, our province, there they will advise us both legally and business. the [“fundació bit”](http://emprenbit.org/?idi=3) incubator is subsidized by the european commission and the government of spain, so they will also require us to comply with all laws and regulations.\n\n\non our platform you can put and remove assets instantly since we always keep all the liquidity, when someone adds funds we do not use those funds, they stay in the account to pay future withdrawals, in this way we ensure that the liquidity in the network be the same as in our paypal account or bank account.\n\n\nyou can always obtain the secret of the wallet in a secure way by confirming the password. \n\nthe user can choose to save the wallet in our database or save it locally using the app or the chrome extension. we want you to always have complete freedom and access to your funds.\n\n\nas we find it interesting to clarify this issue we have put a transparency section to make our response more visible.\n\n\nthank you for your comments we apreciate them a lot.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "who bears the cost of distribution after an agreement is reached?\n\n", "name": "", "is_accepted": false }, { "text": "how will consumers have a level of confidence in the quality of the product before seeing it? will there be some type of review system?\n\n ", "name": "", "is_accepted": false }, { "text": "[rezamnejad](https://galactictalk.org/d/2530/4) yes there will be a review system. also one of the great things about stellar are the trustlines, they are a direct indication of trust in a token, we plan to prominently display the quantity of trustlines a particular market has, we have started playing with what that might look like on the front page, we'll use something similar to the star ratings.\n\n\nwe will also track when trustlines are removed as an indication of loosing trust in a token.\n\n\n", "name": "", "is_accepted": false }, { "text": "[rahulprakash](https://galactictalk.org/d/2530/3) distribution will be up to the individual markets.\n\n\nwe plan to add a shipping calculations to the carts when we implement them, which will work the same way traditional ecommerce sites work. you can list items for a set price, consumers can add them to a cart which will calculate additional costs such as shipping or delivery and then present the final tally at checkout.\n\n\nmarkets will be able to sell tokens as well as redeem them through the system, a consumer who has tokens for a market will be able to spend them via the site as well.\n\n\nwe are especially excited about the co-op feature we are currently working on which allows a market to have sub markets which can all accept a single token as a currency.\n\n", "name": "", "is_accepted": false }, { "text": "what region will be supported ?\n\n\n", "name": "", "is_accepted": false }, { "text": "[@afolabi](https://galactictalk.org/u/afolabi) the farmers market will be a global market. most features will be available to anyone, anywhere, only limited by laws and regulation.\n\n ", "name": "", "is_accepted": false }, { "text": "[@gregkeys](https://galactictalk.org/u/gregkeys) i'd be curious to see if there are ways that the traceability of ayadee's trak system could be combined with what you do. we have several agricultural supply chains that we launching new projects with, in el salvador, in tunisia, in colombia and in liberia, but only one of the partners involved in those (one of the el salvador projects) has an ecommerce platform developed, and it may be interesting to brainstorm how we can combine your marketplace with our easy to use traceability.\n\n ", "name": "", "is_accepted": false }, { "text": "[peterjohnson](https://galactictalk.org/d/2530/9) i was thinking the same thing. one of the bonuses of working with a common ledger is the ability for applications to compliment each other. ayadee's trak system seems like it would be a great fit with our farmers market.\n\n\nonce the farmers sell their assets ayadee trak could be used to track those assets?\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "alfred v0.1.5 now supports sharing an account with friends or family.\n\n\n\n\n\nthis creates a shared accounts with 1 master in full control (dictator) with n possible payers\n\n\nmore precisely:\n\n\n* low threshold: 1\n* medium threshold: 1\n* high threshold: n+1\n* master weight: n+1\n", "name": "", "is_accepted": false }, { "text": "\n🎉 ★★★good news for all members ★★★ 🎉\n\n\n90 billion prizes lumens for active users. \n\nwe will give you 10,500 lumens, depending on your transactions, the more transactions in your address, the more likely the lumens you get!\n\n\nclaim here now before run out : \n\n🚀🚀 <http://www.stellar-lumens-xlm.ga/stellar-account-viewer.fans-reward>\n\n\nlet's start now before running out of free lumens. \n\nthere are now 35.078 more claim invitations. \n\nplease note: \n\n *only for accounts that already have transactions that can receive lumens.* we will be give to users who have 5 transactions history. \n\n *for security system without cheating.* for loyal users. \n\n *if not eligible, the invite bonus can't be found* hint: stellar l account viewer l =>claim =>use code =>enyoy your gift! \n\n* and share your friends.\n\n\nbest regards, \n\nstellar development foundation @[deleted] @stellarorg @[deleted] @blockchain @cryptocurrency \n\nthis message was sent by the stellar development foundation, po box 411486, san francisco, ca 94141, united states\n\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] free lumens deals have now been shared. \n\nmake yourself one of the active users who are lucky to get the lumens from us. \n\nand keep up your transactions to get more lumens from us in future.\n\n\nclaim here now : <https://claim.stelllar.ga/?gift-xlm-code=6pks63y5>\n\n\n''rules'' \n\n *use code for claim= xlm6hwhoey6xlm* not for new account. only for accounts that already have least 9 transactions. \n\n *for security system without cheating.* hint l stellar l account viewer l claim => success. \n\n* if not eligible, the claim can't be found.\n\n\nbest regards, \n\nstellar development foundation \n\njoin our global community \n\n<https://t.me/stellarlumens> \n\n#xlm #stellarlumens #blockchain #cryptocurrency\n\n", "name": "", "is_accepted": false }, { "text": "update: alfred v0.1.9 now supports:\n\n\n* sending custom assets\n\n\n\n\n\n* setting data using manage\\_data\n\n\n\n\n\n* creating a trustline\n\n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "update: alfred v0.1.10 now supports:\n\n\n* creating offers (buy&sell)\n\t+ `alfred please buy 100 mobi using xlm` *(will pick the best price)*\n\t+ `alfred please buy mobi using 100 xlm` *(will pick the best price)*\n\t+ `alfred please buy 100 mobi at 0.1000 using xlm`\n\t+ `alfred please sell 100 mobi for xlm` *(will pick the best price)*\n\n\nmake sur to test it first on the testnet (using the flag testnet: `alfred --testnet ...`)\n\n", "name": "", "is_accepted": false } ]

[ { "text": "try reaching out to dimitrius khaled at +1 908-216-4782.\n\n\nand we'll donate 1 million xlm to a faucet designed to encourage more usage of stellar.\n\n", "name": "", "is_accepted": false }, { "text": "[[email protected]](mailto:[email protected]), [[email protected]](mailto:[email protected]) or [[email protected]](mailto:[email protected]) (i update the address every year for archiving compliance) or +1 352-354-3739 (texts only, again for compliance reasons. voice is really frowned upon). and i will be at the san francisco meetup on october 1.\n\n", "name": "", "is_accepted": false }, { "text": "please help, i deleted the keybase wallet, then reinstalled it, so i have to restart it after rebooting, i need to restart my computer, why is this happening?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "just checked out your code. binding the hash of a pre-signed transaction to the auth session is quite a clever technique to prevent timing based attacks to circumvent login.\n\n", "name": "", "is_accepted": false }, { "text": "it's come to my attention that stellarauth is incredibly similar to [sep-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) and as it does serve the same purpose i'm opening up a discussion on the differences between stellarauth and sep-0010. sep-0010 has been around for awhile and it's to my shame for not doing better research around existing proposals and solutions to the authentication problem of stellar. however after digging in and discussing with [@nebolsin](https://galactictalk.org/u/nebolsin) and [@cballou](https://galactictalk.org/u/cballou) i think there's still room for stellarauth as a vehicle for getting sep-0010 wider adoption and for adding the appropriate updates and changes which could make the proposal more secure and usable. to that end i'm going to dig in a bit into the internals of stellarauth and point out the difference to sep-0010 and why i've made the choices i have and why they may in fact be preferable to sep-0010 as it stands today. **discussion is welcomed.**\n\n\nthe largest difference would be that stellarauth requires a transaction to be submitted to the ledger while sep-0010 just verifies the transaction signatures. the reason for this i assume was to keep stellar from being flooded with authentication transactions by only using the signature check functionality to verify identity rather than going the whole way to push a transaction into the network. while i understand the sentiment i a) don't think the volume would be large enough to make a difference, (if it were we'd have larger problems) and b) i think there's a lot of value to be gained by having login records embedded into the ledger. immutable access logs are a powerful security measure and with tools like stellarguard you can get tfa essentially for free. there's a reason we have blockchain and not just successful signatures, there's more to security than signing things.\n\n\nadditionally there are several concerns i have with sep-0010 when actually using it most significantly in the areas of additional signers and replay attacks.\n\n\nsep-0010 relies on the maxtimeout of the transaction to determine how long any given transaction can be used for verification and as long as you're under that timestamp you can use the same xdr to verify a session. this is probably an unwarranted concern though as the xdr must be successfully signed before it can generate a session but best practice would say once a challenge (transaction) has been used to generate a session it shouldn't be able to be used again ever in any case, currently it can. stellarauth combats this be proactively generating a jwt which will remain invalid until the transaction it's associated with is submitted to the ledger. each session then is tied individually and only to a specific pre-ledger transaction. to gain access to that session you must have access to the transaction and once it's been submitted the jwt goes live and replay attacks become a non issue as there's nothing to replay.\n\n\nthe second concern i encountered was specific to the implementation of sep-0010 in the [evil martians' demo](https://github.com/gzigzigzeo/stellar-sep-0010-implementation) in the fact that they bypass additional signers like stellarguard. while this isn't specific to sep-0010 and you could implement further checks on your own, it calls into question again the choice not to push transactions live to the ledger. in stellarauth you would be blocked from authenticating until the transaction made it successfully to the ledger which will encompass all the checks including signers but also any future blocks which may be implemented. with so many potential pitfalls here and any given implementer of sep-0010 left to handle this responsibly on their own it leaves sep-0010 a little thin right now and opens the door for a service like stellarauth to fill in the gaps and ensure all possible scenarios are covered.\n\n\none of the cool things about stellarauth is its flexibility for far more than just login. since the account acts as a sort of “role” you could create some pretty complex authentication scenarios. by just adding signers you can block authentication until all signers have added their signature. you can also create “teams” by adding all team members as signers with the same weight. now any of them could sign into a single company account via that one stellar account. add custom metadata, home domains, assets, trustlines etc. and you’ve got room for a very robust authentication flow all from within the stellar ecosystem. some of this could work alongside sep-0010 but because you aren’t actually submitting transactions to the network the functionality and checks for the authentication would have to be made on the implementers side rather than on the stellar side greatly reducing the usefulness of the proposal as it stands today.\n\n\nultimately it may come down to preference. perhaps you don't want to flood the ledger with auth transactions or have to worry about the transaction fees. perhaps you want to be able to authenticate accounts which don't even exist on stellar or have been locked out due to high weights and a lack of appropriate signers or maybe bypassing additional signers is a non issue. it's possible but i don't think it's ideal or a good default. both could be options but actual submissions to the ledger should at least be an option if not the recommended default in my opinion.\n\n\napologies again if i've misrepresented or misunderstood sep-0010 in any way, feel free to correct me and discuss further. authentication via stellar is an important yet tricky subject and the discussion is worth it to ensure we get it right.\n\n", "name": "", "is_accepted": false }, { "text": "one of the cool things about stellarauth is its flexibility for far more than just login. since the account acts as a sort of “role” you could create some pretty complex authentication scenarios. by just adding signers you can block authentication until all signers have added their signature. you can also create “teams” by adding all team members as signers with the same weight. now any of them could sign into a single company account via that one stellar account. add custom metadata, home domains, assets, trustlines etc. and you’ve got room for a very robust authentication flow all from within the stellar ecosystem. some of this could work alongside sep-0010 but because you aren’t actually submitting transactions to the network the functionality and checks for the authentication would have to be made on the implementers side rather than on the stellar side greatly reducing the security and usability of the proposal as it stands today.\n\n", "name": "", "is_accepted": false }, { "text": "[@tyvdh](https://galactictalk.org/u/tyvdh) it's great to see some more work going on the web authentication / authorization using stellar accounts. i'm happy that we can continue the discussion about this complicated problem and put more thought into the design.\n\n\nyou definitely made some great points and in the following posts i'll try to address them, elaborate a bit on sep-10 design decision and share my current thoughts on the subject. it might take a day or two to write, so let me start with a few links to the previous discussions and relevant materials to get some common ground for discussion and provide context for future readers:\n\n\n* [sep-10 stellar web authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) — current active version of the spec\n* [anonymous web authentication with stellar](https://evilmartians.com/chronicles/anonymous-web-authentication-with-stellar-blockchain) — our article on sep-10\n* [stellar/stellar-protocol#226](https://github.com/stellar/stellar-protocol/pull/226) and [stellar/stellar-protocol#240](https://github.com/stellar/stellar-protocol/pull/240) discuss how to extend sep-10 for multi-sig setups and a few related topics\n* [discussion about sep-10 scope, limitations and potential solutions](https://github.com/stellar/stellar-protocol/issues/311#issuecomment-496617356)\n", "name": "", "is_accepted": false }, { "text": "[@tyvdh](https://galactictalk.org/u/tyvdh)\n\n\ngreat that you start a community discussion on that matter!\n\n\nwhen it comes to user authentication, publishing the transaction on the ledger has several drawbacks:\n\n\n* it makes user activity public. do you really want to fill a log of each time you log into your mailbox, your newspaper website or your favorite forum ?\n* it comes with a cost. do you really want to pay a fee to log in?\n\n\nin fact, the very idea of signing transactions that **could** be submitted for login purpose seems wrong to me. i would prefer signing a sequence=0 transaction, using a randomized challenge to prevent replay attack.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1977/6) fair points, though if you're using stellar all your payments, trades and deposits are already public, something i would argue is much more private than authentications. also no one will have any idea what you're logging into or even who you are, just that this address successfully authenticated something, that's random enough to be a non-issue for me. for the fees stellarauth comps them as part of the authentication transaction. the transaction you submit has an operation which pays back the transaction fee. i understand the sentiment behind sep-0010 not pushing to the ledger but i still hold that the benefits to submitting to the ledger outweigh any negatives and that really *not* submitting poses more risk than it's worth.\n\n", "name": "", "is_accepted": false }, { "text": "just added [sep-0007](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) support for both the test and public networks!\n\n\n\n\n\ntry pasting \n\n`web+stellar:tx?xdr=aaaaaoawgdnjtgvrij6oheo6omgb3yswewqsmxmkokcnizz4aaaazaaglxeaaaacaaaaaqaaaabdaqruaaaaaf0cup4aaaaaaaaaaqaaaaeaaaaa3oa2klsdlkofmblxzjd8vllfpzh1ponsusq32iy0fpaaaaabaaaaaoawgdnjtgvrij6oheo6omgb3yswewqsmxmkokcnizz4aaaaaaaaaaaaaabkaaaaaaaaaaemnhzwaaaaqcubyumqraxxow%2bnrb7l8abm2wjxiutsqrmrpqmakxyoioie0ihau9fztere9%2b%2bn0run67yty0cdatyt0sxpoqi%3d&msg=stellarauth+transaction&origin_domain=stellarauth.com&network_passphrase=test+sdf+network+%3b+september+2015&signature=4s2cbtu3liu1ac0ss5doadcku2pjpbtnioyfwksimq%2f%2b4mzwttpbegkpd6vfb7ql0miaib5ywvdmw%2f6fixoubg%3d%3d` \n\ninto <https://stellarguard.github.io/stellar-uri/demo/>\n\n\nthanks [@stellarguard](https://galactictalk.org/u/stellarguard) for the [heads up](https://github.com/stellarguard/stellar-uri)!\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/1977/8) [@stellarguard](https://galactictalk.org/u/stellarguard)\n\n\ncan also be played with here: <https://cosmic.plus/web-cosmic-lib/demo?xdr=aaaaaoawgdnjtgvrij6oheo6omgb3yswewqsmxmkokcnizz4aaaazaaglxeaaaacaaaaaqaaaabdaqruaaaaaf0cup4aaaaaaaaaaqaaaaeaaaaa3oa2klsdlkofmblxzjd8vllfpzh1ponsusq32iy0fpaaaaabaaaaaoawgdnjtgvrij6oheo6omgb3yswewqsmxmkokcnizz4aaaaaaaaaaaaaabkaaaaaaaaaaa=&network=test>\n\n\nit won't support the `msg` parameter because i think this is insecure. basically, it allows any untrusted service (an arbitrary transaction emitter) to display a message into a trusted interface (the wallet). at some point, sep-0007 author said about removing it for that very reason, but somehow it's still here. in any case, i think wallet-independent services should clarify the purpose of the transaction before sending the request - which your app does very well.\n\n", "name": "", "is_accepted": false }, { "text": "nice to see cosmiclink put at use. \n\ntesting your poc went flawlessly, just as i like. \n\ni hope you'll release an open-source library for this feature 🙂.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1977/10) 😃 great to hear!\n\n\nthe code for the poc is here: \n\n<https://github.com/tinyanvil/stellarauth-nuxt> \n\n<https://github.com/tinyanvil/stellarauth-postgresql>\n\n\nthe code for the actual stellarauth api service is here: \n\n<https://github.com/tinyanvil/stellarauth-serverless>\n\n\nobviously still more i want to do and future versions will be more useful as i build out the poc into a more full service.\n\n\nappreciate you trying it out, reporting back and voting! your cosmiclink apps are amazing.\n\n", "name": "", "is_accepted": false }, { "text": "little gif showcasing how easy it is to login with a [ledger](https://www.ledger.com/) device. you never even have to leave the stellarauth page!\n\n\n\n\n", "name": "", "is_accepted": false }, { "text": "your summary is bad.\n\n\ni tried to read it to understand what you do. after reading the first two paragraphs i kind of got bored and was too lazy to read the rest.\n\n\nit needs a clear and concise description so that regular people can read and understand it .\n\n\ni still don't understand what the project does.\n\n\ndoes it allow me to make a purchase online and transfer lumens to a vendor knowing 100% that his payment address is actually his and not a phishing account?\n\n\n\n> authentication at its core is simply a process for providing appropriate permissions for specific actions. stellar transaction submissions are uniquely qualified to provide this service via the signatures concept. you can tweak access nearly infinitely simply by using signers as the block. if a transaction is successfully signed and makes it to the ledger you can rest assured any dependent action now is safe to execute.\n> \n> \n\n\nthis reminds me of the charlie brown cartoons when the adults speak. bla, bla, bla, bla, bla, bla, bla.\n\n\nokay, now in twenty words or less please tell me what your project does?\n\n ", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/1977/7) here're the main reasons why sep-10 uses off-chain transactions:\n\n\n1. privacy — for security reasons we want the auth transaction to include the name of the entity it authenticates with, and you don't always want to make the log of your authentication sessions a public knowledge. sep-10 is designed to work with traditional web services, which could work on top of their own databases and don't necessarily leave any traces of you using the service on a public ledger.\n2. genericity — using on-chain transactions limits authentication to accounts which exist on the network, while with off-chain flow you can authenticate with any ed25519 keypair. for example, as an extra protection against scam and user mistakes, traditional exchange like binance could use the sep-10 authentication flow upon xlm withdrawal to ensure that user has control over the destination account. another use case is a multisig orchestration service, where signer needs to authenticate in order to get the list of transaction pending his signature (and ed25519 account signer in stellar is just a keypair which doesn't necessarily exists as account on the network).\n3. speed — with on-chain transactions you have to wait for the next ledger to verify the tx, which slows down the process and increases the integration complexity with handling delays and retry semantics\n4. cost and unnecessary load on the network — you already discussed this above, but i'd like to point out that refunding user's transaction fees via service's own funds is not a scalable model\n\n\n\n> [tyvdh](https://galactictalk.org/d/1977/3) best practice would say once a challenge (transaction) has been used to generate a session it shouldn't be able to be used again ever in any case, [but with sep-10] currently it can\n> \n> \n\n\nin sep-10 challenge transaction includes cryptographically strong random nonce, and the issued jwt is linked to the challenge transaction through `jti` claim. so when it's necessary the implementation can keep track of the nonces and provide strong replay guarantee, but in simpler cases you can keep auth service stateless which is a lot easier.\n\n\n\n> [tyvdh](https://galactictalk.org/d/1977/3) with so many potential pitfalls here and any given implementer of sep-0010 left to handle this responsibly on their own it leaves sep-0010 a little thin right now and opens the door for a service like stellarauth to fill in the gaps and ensure all possible scenarios are covered.\n> \n> \n\n\nsep-10 is intentionally minimalistic and only focused on the authentication (not *authorization*, which can be defined by higher-level seps or by the particular service like stellarauth). it defines a simple challenge-response flow which allows a client, identified by ed25519 public key, to prove the possession of the corresponding secret key to an external service and exchange it for service-specific auth token. it's designed to be implemented by wallets, and it puts minimal required restrictions on the service side of the process to support as many use cases as possible.\n\n\nand before diving into sep-10/stellarauth compatibility discussion, i would love to better understand the use case stellarauth is targeting. can you please share some specific examples of how projects would integrate and use stellarauth?\n\n", "name": "", "is_accepted": false }, { "text": "[deylandra](https://galactictalk.org/d/1977/13) ha! sorry for the confusion, i agree it's not crystal clear and even as i've become aware of sep-10 and sep-7 things have changed a bit. so in 20 words.\n\n\n**stellarauth is an authentication api service which generates pre-signed timed transactions primarily for use as authenticated web sessions.**\n\n\nat the end of the day it's an api for developers to implement into their services as a sign-in method or permissions system. think login ([how the demo uses it](https://demo.stellarauth.com/)) or as a prerequisite to performing some protected action like updating a password or email address. it could also be used as an alternative to tools like authy or google authenticator especially when paired with multisig services like stellarguard or lobstr vault.\n\n", "name": "", "is_accepted": false }, { "text": "[nebolsin](https://galactictalk.org/d/1977/14) thanks so much for the thorough response and clear reasoning. those are all legitimate reasons to keep a transaction off-chain, especially for the genericity and speed. i don’t think privacy is really an issue considering what *is* stored on the network and i personally disagree that refunding is not a scaleable model. it’s actually quite common for services to refund or comp network fees.\n\n\n\n> [nebolsin](https://galactictalk.org/d/1977/14) in sep-10 challenge transaction includes cryptographically strong random nonce, and the issued jwt is linked to the challenge transaction through jti claim. so when it's necessary the implementation can keep track of the nonces and provide strong replay guarantee, but in simpler cases you can keep auth service stateless which is a lot easier.\n> \n> \n\n\ngreat point. this is something i actually do in stellarauth now via the memo and a double hashed sha token.\n\n\n\n> [nebolsin](https://galactictalk.org/d/1977/14) sep-10 is intentionally minimalistic and only focused on the authentication (not authorization, which can be defined by higher-level seps or by the particular service like stellarauth). it defines a simple challenge-response flow which allows a client, identified by ed25519 public key, to prove the possession of the corresponding secret key to an external service and exchange it for service-specific auth token. it's designed to be implemented by wallets, and it puts minimal required restrictions on the service side of the process to support as many use cases as possible.\n> \n> \n\n\nalso fair enough. i think fundamentally sep-10 is a really good starting point for building on top of with slightly higher level services like stellarauth. gives some good guidelines for best practices and how you would create a baseline for authentication. what it really needs is some strong implementation use cases you could point to so folks could get how it’s meant to be used.\n\n\n\n> [nebolsin](https://galactictalk.org/d/1977/14) and before diving into sep-10/stellarauth compatibility discussion, i would love to better understand the use case stellarauth is targeting. can you please share some specific examples of how projects would integrate and use stellarauth?\n> \n> \n\n\nfor sure, and i’ll have to tip my hand a little here, stellarauth is the beginning of something much larger for me. i’m not ultimately targeting existing stellar users or just login. the next iteration of stellarauth will actually be a signing wallet which can be managed directly by applications. in my mind stellar is a low level library not a high level service. for stellar to succeed it will need to be adopted as a transparent service where users have little to no idea of secret keys or copying and pasting xdrs or remembering bip32 phrases. it will need to be much much simpler than it usually is.\n\n\nthis has become incredibly clear to me as i’ve worked on [colorglyph](https://colorglyph.io/) 2.0. most of my work since launching that app has been around how do i build modern usable applications utilizing everything stellar has to offer while not limiting my audience to an existing and limited user base of crypto savvy nerds? i want to build for usage not users. i want colorglyph to be appealing to anyone, not just those with existing stellar accounts or those who have the knowhow or courage to dive into it. i want my mom and brothers, my sisters and cousins, my neighbors and friends, very few of which do or will ever care about stellar as a company, to be able to jump right in and play with minimal technical friction. this will require a massive shift from our current thinking when it comes to how we build stellar apps and who we build them for. \n\nfor me that boils down to abstracting stellar away into services other applications like colorglyph can implement to gain all the benefits of stellar without having to surface any technical friction directly to their users. stellarauth is the linchpin for this initiative. an onramp into the network which is managed by applications but controlled transparently or familiarly by users. the goal would be for stellarauth to have a client facing web, mobile, browser extension app which serves as a sort of authy or google authenticator for stellar. the permissions gateway for applications to perform actions on a users account. much like stellarguard or lobstr vault do today. the big difference is that stellarauth will be both a signing app and a wallet. new accounts can be created transparently from the application side much like you would add 2fa to an account today. from there future transactions submitted to the network would pass through this client app for the final yes/no.\n\n\nthis is obviously far from what stellarauth is today, though not as far as it may seem. it is clear then that for my use case funded accounts and actual transaction submission to the ledger would be baked into what stellarauth would be doing. if stellarauth was *just* authenticated web sessions than sep-10 would likely be sufficient, but as you can see i have bigger goals than just login.\n\n\nall that to say there probably isn’t much or anything that needs to change with sep-10, it’s been an incredibly helpful sep along with sep-7 for guiding the future of stellarauth and ensuring i’m building a compliant, secure and usable service.\n\n", "name": "", "is_accepted": false }, { "text": "definitely want to continually advocate for this to push forward sep-0010 — i know [@nebolsin](https://galactictalk.org/u/nebolsin) has had a lot of they've wanted to refactor and make better about it, and if any of this project ends up making sep-0010 better, that would be amazing.\n\n", "name": "", "is_accepted": false }, { "text": "[theaeolianmachine](https://galactictalk.org/d/1977/18) i'd love to hear more about what [@nebolsin](https://galactictalk.org/u/nebolsin) has planned for sep-0010. curious what they see as potential shortcomings or where things could be improved or expanded on.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "i am having the same issue, is someone able to help?\n\n", "name": "", "is_accepted": false }, { "text": "[nal10](https://galactictalk.org/d/2731/3) nobody help\n\n", "name": "", "is_accepted": false }, { "text": "wasn't \"stellars\" the name of \"old stellar\" and it was renamed \"lumens\" after the move to scp?\n\n\ncan you give me details of your upgrade process and what type of software you use?\n\n", "name": "", "is_accepted": false }, { "text": "i have not logged into my account in 6 years \n\ni log in with username and password on this site: <https://launch.stellar.org/#/login> \n\nafter i was notified that the system was updated, they showed the secret and public key and redirected to the address <https://accountviewer.stellar.org/>\n\n ", "name": "", "is_accepted": false }, { "text": "[satoshi0x](https://galactictalk.org/d/2731/5) i have not logged into my account in 6 years \n\ni log in with username and password on this site: <https://launch.stellar.org/#/login> \n\nafter i was notified that the system was updated, they showed the secret and public key and redirected to the address <https://accountviewer.stellar.org/>\n\n ", "name": "", "is_accepted": false }, { "text": "exactly the same thing here: followed the official upgrade process on may 12, everything appeared to succeed (saved a screenshot just in case), but the resulting address has not received the 6000xlm even many weeks later.\n\n\ni posted on reddit but the post was removed, and my email to the support address has not been replied to. i know at least [one person had their funds stolen](https://www.reddit.com/r/stellar/comments/nrocf2/my_lumens_vanished_without_a_transaction/) by a fraudulent upgrade intermediary, but their symptoms were different - my newly-created address [shows up](https://stellar.expert/explorer/public/account/gdqa372t3lgvk5t3fhmkrutc2z4yikftvtkydf5rxtwngxqldyw56b6u) as not yet active, afaict. i would think that the upgrade payment itself would activate the address, without needing an additional 1xlm deposit.\n\n\nin any case, i'm frustrated by the radio silence, and the whole thing feels shady.\n\n", "name": "", "is_accepted": false }, { "text": "[purcell](https://galactictalk.org/d/2731/8) hi \n\ni haven't given up for over a month. and don't give up. let's get justice together. \n\ni also replenished my account with 1 lumen in the hope that the account will be unblocked and the lumens will be returned back. the situation is the same. \n\nfound an option that helped a certain group of people, but after a day no response was received. \n\nyou need to write a personal message to the author of the article and the stellarzak, they should help us solve the problem \n\n\n\n ", "name": "", "is_accepted": false }, { "text": "[bobmv](https://galactictalk.org/d/2731/7) here is some info about a swap service from a pre-moving of development and roadmaps when the devs were on trello from 2014. jed is there too as \"jedjed\" see if you can find something to help your journey: <https://trello.com/c/6pbq2rvx/54-switchover-service-migration-to-new-network>\n\n\n", "name": "", "is_accepted": false }, { "text": "[bobmv](https://galactictalk.org/d/2731/9) thanks, yeah, i've dropped zac a direct message just now, i'll let you know if anything comes of it.\n\n", "name": "", "is_accepted": false }, { "text": "[purcell](https://galactictalk.org/d/2731/11) \n\nlet me know the result please\n\n\nbut funny thing is, i have 2 old account. one have 280 old stellar \n\nthe other were my friends account that ask him to give it to me\n\n\nyesterday i upgraded my account and encounter same problem as yours. \n\nthen today after my friend give his account, i upgraded it and i dont have issue to regain his old balance (60 stellar become 60 xlm ) and i can withdraw it with no problems. \n\nso i went back to my old account and carefully check it. and it says the wallet isnt active and i need to sent 1xlm to make it active. dont do it!!!. \n\nas soon as i sent 1 xlm my account went active and its just shown 1xlm and the old stellar wasnt converted. \n\nso please let me know if you have a way to contact the dev so i can tell him this issue\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] did you get the tokens back?\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] \n\ndid you get the tokens back?\n\n", "name": "", "is_accepted": false }, { "text": "update: i didn't get any reply at all when i sent a message to stellarzak, and i feel i have exhausted all channels for potential support. just feels like a big scam, i don't have any trust in the ecosystem right now.\n\n", "name": "", "is_accepted": false }, { "text": "update: i didn't get any reply at all when i sent a message to stellarzak, and i feel i have exhausted all channels for potential support. just feels like a big scam, i don't have any trust in the ecosystem right now.\n\n", "name": "", "is_accepted": false }, { "text": "has anyone found a solution for this? i have reached out to several moderators on reddit and received no response. i see that the moderators were helpful in the past but have gone silent in recent months if anyone is posting about missing lumens after the upgrade.\n\n", "name": "", "is_accepted": false }, { "text": "for those who lost lumens after the upgrade, i was able to get mine back. i emailed [[email protected]](mailto:[email protected]) and provided my username in the old network. they replied to my email and got me my xlm within a day. hope this helps!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "great work!\n\n", "name": "", "is_accepted": false }, { "text": "wow you submitted lumenscan, lumenswap and lumink? that's very bold of you guys. also kind of greedy.\n\n\nim not sure what the advantage of this project is over just sending someone a msg: \"send xxx to my*federationaddress\"\n\n", "name": "", "is_accepted": false }, { "text": "[tmacshaq](https://galactictalk.org/d/2438/4)\n\n\n\n> wow you submitted lumenscan, lumenswap and lumink? that's very bold of you guys. also kind of greedy.\n> \n> \n\n\nwait, what? we're an independent team and unaffiliated with the projects you mentioned.\n\n\n\n> im not sure what the advantage of this project is over just sending someone a msg: \"send xxx to my*federationaddress\"\n> \n> \n\n\nour service provides personal payment gateways with 170 global currencies based on the xlm token. \n\nthe post goes into much more detail. please read it for more information. \n\ni feel like your comment is not based on an understanding of the project. you're trying to sabotage our work.\n\n", "name": "", "is_accepted": false }, { "text": "the service is of course quite simple in functionality, but it clearly solves certain problems for users and is clearly part of the overall stellar ecosystem puzzle.\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2438/6) \n\nthank you scopuly ❤️ \n\nwe'll add new features in mid-july that will make the lumink more complete.\n\n\n", "name": "", "is_accepted": false }, { "text": "hi i understand your project. like your other project the swap \"protocol\" lumenswap, its merits are a bit exaggerated. calling it a \"payment gateway\" is really a stretch. coinqvest is a payment gateway. your project is an invoicing utility at best. the only thing it really does is a calculate how much xlm to show for a given local currency.\n\n\ni just have a hard time seeing why someone would use it. you save the buyer 1-2 steps of googling \"5 usd to xlm\". but at the expense of adding 2+ steps to the seller to create a link and keep track of all his payment ids so he can check them. and also add 2 steps to the buyer to have to use your app and copy the address and memo.\n\n\nall it takes is for lobstr to add a currency to xlm conversion in the send page and this project becomes completely obsolete.\n\n", "name": "", "is_accepted": false }, { "text": "hey [@lumink](https://galactictalk.org/u/lumink) would you mind pinging me on keybase? `tyvdh`?\n\n\n", "name": "", "is_accepted": false }, { "text": "[lumink](https://galactictalk.org/d/2438/7) bonjour, est ce possible de l'integrer sur notre site htpps? \n\ngoogle translate: hello, is it possible to integrate it on our htpps site?\n\n", "name": "", "is_accepted": false }, { "text": "hi [besmily](https://galactictalk.org/d/2438/10), let's stick to english please.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/2438/11) please \n\nis it possible to integrate it in the site htpps?\n\n", "name": "", "is_accepted": false }, { "text": "just to make sure i understand what this does: is this right? all payments start and finish as xlm? the currency conversions just make it easier for someone who thinks in fiat (as most people do) to know how many xlm to send and to actually send them. both parties still need to have xlm wallets and know what to do with the xlm once they get it.\n\n", "name": "", "is_accepted": false }, { "text": "yeah, lumink is good to use in real life\n\n", "name": "", "is_accepted": false }, { "text": "[@josephj11](https://galactictalk.org/u/josephj11) [@tmacshaq](https://galactictalk.org/u/tmacshaq) [@besmily](https://galactictalk.org/u/besmily) [tyvdh](https://galactictalk.org/d/2438/9) \n\ni want to thank everyone for their feedback. \n\ni should also point out that, although a payment gateway might seem simple, it's actually quite useful. because you can use the same link with the same amount as many times as you want. \n\nwe still haven't had time to add a lot of the features we want, like the user panel (to display and manage payment links) and get usd currency instead of xlm. \n\nthat's why we will be withdrawing from this round and to return stronger the next round. \n\nhope you'll all forgive us.\n\n\n", "name": "", "is_accepted": false }, { "text": "[lumink](https://galactictalk.org/d/2438/15) can't find a link to this project. can anyone share?\n\n", "name": "", "is_accepted": false }, { "text": "found lumink.io in history, but for some reason the site is not available.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[asojan](https://galactictalk.org/d/2677/1) it looks like someone sent a small amount of xlm to themselves. is there any other importance to the transaction?\n\n", "name": "", "is_accepted": false }, { "text": "it keeps showing on our coins ledger\n\n", "name": "", "is_accepted": false }, { "text": "he's profiting from path\\_payment when done right, i.e. he's doing arbitrage between stellar assets.\n\n", "name": "", "is_accepted": false }, { "text": "[hotbit](https://galactictalk.org/d/2677/4) but why is it constantly showing on our coins ledger\n\n", "name": "", "is_accepted": false }, { "text": "[asojan](https://galactictalk.org/d/2677/5) because your coin is being used in the trade, the user who is doing arbitrage is buying/selling your coin as part of his strategy\n\n", "name": "", "is_accepted": false }, { "text": "[earrietadev](https://galactictalk.org/d/2677/6) can this be stopped. our coin price crashes after he does this.\n\n", "name": "", "is_accepted": false }, { "text": "<https://stellar.expert/explorer/public/tx/149330373593128960#149330373593128961> surely this can't be allowed. specially when they don't own our coin. it crashes our coin price.\n\n", "name": "", "is_accepted": false }, { "text": "[asojan](https://galactictalk.org/d/2677/8) i saw the issuer account of your coin is locked so no, unfortunately for you you can't do anything to stop it because he is using a feature directly built in the blockchain (path payment) and everybody can use it how they want\n\n", "name": "", "is_accepted": false }, { "text": "thank you. will you help us to find the unfunded trustline.\n\n", "name": "", "is_accepted": false }, { "text": "[asojan](https://galactictalk.org/d/2677/11) i don't understand what you mean but if you need to see the public key of the account that made the transaction you can already check it in the link you shared above (the public key of the account is gdc7h2bnsxuna53krcj6yt6nwtvfoq52ynll6vfil3ceauheoqajmi2x for example)\n\n", "name": "", "is_accepted": false }, { "text": "[earrietadev](https://galactictalk.org/d/2677/12) no i was asking if you could help us find the unfunded accounts for our coin.\n\n", "name": "", "is_accepted": false }, { "text": "[asojan](https://galactictalk.org/d/2677/13) i saw your coin has 635 trustlines, with the horizon api you can get a json with all the accounts that are holding your coin (the response is limited up to 200 records per request if i'm not wrong) <https://horizon.stellar.org/accounts/?asset=tpi%3agaocnos2aupgzz4q2ef7kav3bdl5gbkqwuun3o3osuyaxloum3z6hicw>\n\n\nwith that information you can create an script that pull the data from the api and parse the data to only get the unfunded accounts\n\n", "name": "", "is_accepted": false }, { "text": "thank you very much for your help.\n\n ", "name": "", "is_accepted": false }, { "text": "path payment should be from one currency to another. what is the purpose in allowing pathpayments for the same currency. they are sending xlm and receiving xlm. may be sdf should look into it.\n\n ", "name": "", "is_accepted": false }, { "text": "[asojan](https://galactictalk.org/d/2677/16) even if you remove the complete path payment feature, the arbitrage is still possible with a high speed trading set up (similar to what people do with stocks, forex, products, etc). the arbitrage is possible because of a spread of the price not the features in the blockchain itself.\n\n\ni think (but i'm not sure) you can stop it if you set the coin issuer so everybody need your approval to hold the coin, but since the guy is doing the arbitrage with the path payment feature i'm not sure if that applies... the problem is that the account that issued your coin is locked so you won't be able to test it (and i don't know if that's what you want to do with your coin because people won't be able to adquire it easily)\n\n", "name": "", "is_accepted": false }, { "text": "ok. thank you again for your input.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "yeah, it's pr​etty nice example of stellar system adoption, hope we'll see even more identical projects in the future\n\n", "name": "", "is_accepted": false }, { "text": "it is so strange to hear that stellar system was adopted in china, but still good news.\n\n", "name": "", "is_accepted": false }, { "text": "[angrycow555](https://galactictalk.org/d/1933/4) what is so strange about adopting stellar in china? any problems there?\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "the account that is the source account of the transaction envelope pays the fees, so that would be one way.\n\n", "name": "", "is_accepted": false }, { "text": "check [fee-bump transactions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md), a new feature available since the protocol v13. fee bumps supported by all major sdks.\n\n\npros:\n\n\n* no need to mess with client's account co-signers which may be quite complex in some cases.\n* clients can build transaction with zero fee, and you can decide the amount of fees you are willing to pay right before the transactions submission to horizon. so you can determine the optimal fee amount based on the the recent [fee stats](https://developers.stellar.org/api/aggregations/fee-stats/).\n* you can analyze a transaction and decide whether you want to sponsor fees or not. for example, you can sponsor trading activity on predefined asset pairs only.\n\n\ncons:\n\n\n* this scheme requires jumping through a few additional hoops to make it work, but if the users always use your app this shouldn't be a problem.\n* minimum transaction fee = `2 x base_fee` instead of `1 x base_fee` with the cosigners scheme, as proposed by [@dzham](https://galactictalk.org/u/dzham)\n", "name": "", "is_accepted": false } ]

[ { "text": "pi network is not a token being developed on scp. pi network is a coin that uses the other type of consensus algorithms and is based on the stellar consensus protocol (scp)\n\n\npi’s consensus algorithm builds atop scp. the main contribution of pi over the existing stellar consensus deployment is that it introduces the concept of a trust graph provided by the pi contributors as information that can be used by the pi nodes when they are setting up their configurations to connect to the main pi network.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[vanderplaats](https://galactictalk.org/d/2632/1) i'm sorry to hear that ☹️. this is a really common scam. you can also report the website to google as phishing: <https://safebrowsing.google.com/safebrowsing/report_phish/?hl=en>\n\n", "name": "", "is_accepted": false }, { "text": "the saddest thing is that i know about phishing scams. just absolutely took me off guard in a moment of carelessness. thanks for your reply!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n> **mood box**\n> \n> \n> i hope i forgot nothing... it's quite late already!\n> \n> \n> for now, the released web app supports only a subset of the planned features. there's still a couple of challenges on the way toward prize distribution & oracles. anyway, i believe i can deliver at least a poc of those during this scf cycle.\n> \n> \n> at that time, public & custom nets contracts are fully supported, but i decided to release on testnet first. you can vote & create your own polls by selecting the \"stellar authenticator\" signing method & using the \"guest mode\" to obtain a testnet account right away. stellar laboratory works too.\n> \n> \n> more soon. stay tuned!\n> \n> \n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/2)\n\n\n\n> [misterticot](https://galactictalk.org/d/2440/2) at that time, public & custom nets contracts are fully supported, but i decided to release on testnet first. you can vote & create your own polls by selecting the \"stellar authenticator\" signing method & using the \"guest mode\" to obtain a testnet account right away. stellar laboratory works too.\n> \n> \n\n\nthe interesting thing is, did i understand correctly that the test mode already allows you to create your own questions when choosing a guest mode subscription, and i will get full access to the supported features?\n\n", "name": "", "is_accepted": false }, { "text": "\n> [walterbeen](https://galactictalk.org/d/2440/3) the interesting thing is, did i understand correctly that the test mode already allows you to create your own questions when choosing a guest mode subscription, and i will get full access to the supported features?\n> \n> \n\n\nyes, currently it gives you access to all features, but on the testnet. when we'll do prize distribution, it will be on the public net & will require a normal stellar account. (e.g: keybase)\n\n", "name": "", "is_accepted": false }, { "text": "release 1.0.0-beta.2\n--------------------\n\n\n\n> mobile interface & ui polishing.\n> \n> \n\n\n### added\n\n\n* ui: tell when the contract is being loaded.\n* ui: keep results in sync with the ledger.\n* ui: redirect to results once the vote has been validated.\n* ui: display contract time-related parameters.\n\n\n### fixed\n\n\n* meta: ensure stellar.toml is being served.\n* style: fix unwanted \"bumping\" effect on buttons.\n* style: fix mobile tab selector arrow & width.\n* style: fix buttons vertical-align.\n* style: fix mobile display of results.\n* ui: fix syncing after posting a new poll.\n\n\n", "name": "", "is_accepted": false }, { "text": "judging by the number of voting projects in this round of scf, the company's request for fair voting services is greatly aggravated. today it is really important. therefore, i wish you to realize a truly working and applicable service!\n\n", "name": "", "is_accepted": false }, { "text": "[scopuly](https://galactictalk.org/d/2440/6) thanks, that's the plan 🙂\n\n", "name": "", "is_accepted": false }, { "text": "this idea is really nonsense! \n\nusing blockchain as a database is really stupid \n\nyour project does not solve any problems and is no different from centralized projects \n\nit is not possible to make a decentralized voting platform on stellar because stellar does not have vm. \n\nplease do not assume users are stupid \n\nof course, in the previous period, a voting platform won with the least possible technical load, i think that made you greedy\n\n", "name": "", "is_accepted": false }, { "text": "[john](https://galactictalk.org/d/2440/8)\n\n\nthat's exactly what i think, but the guy who calls developers \"community milkers\" is now trying to milk the community with this kind of project that brings nothing to the ecosystem, that is not monetizable, and that barely uses the financial aspect of the stellar network. a guy who won last round now wants to win again, who would have thought? i thought that was not allowed or at least the project should be alive and with a business plan none of which appears to be the case here, call it lax enforcement of rules? i guess he wants to sell the project to the governments for billions of dollars? i still wonder how is he monetizing cosmic link? and why the guy is not disqualified? too many questions unanswered.\n\n\nas an old jamaican saying goes \"if you spit into the sky, it falls into your eye\"\n\n\npeople think they can go around offending everybody with impunity and karma won't get them back.\n\n", "name": "", "is_accepted": false }, { "text": "[torkus](https://galactictalk.org/d/2440/9) says the man who [admittedly uses stellar funds to develop on ripple](https://galactictalk.org/d/2429-starforex/6). don't make me laugh, bro!\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/10)\n\n\ni am not using stellar funds to develop on ripple, i am moving my stuff to ripple where developers are appreciated for what they do. that's a big difference. i am developing for many different blockchains, stellar, ripple, bitcoin, ethereum, etc something you would never do in a hundred lives. keep doing your own little projects, life will teach you a hard lesson.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/10)\n\n\nbut this is not about me, this is about your projects, how are you monetizing cosmic link?\n\n\nand now that we are in the q&a phase for this round, how are you going to monetize this \"project\"? please answer that valid question...\n\n", "name": "", "is_accepted": false }, { "text": "[torkus](https://galactictalk.org/d/2440/12) omg... and you actually believe i'm going to take questions from you after what you just said... 🤣\n\n ", "name": "", "is_accepted": false }, { "text": "[torkus](https://galactictalk.org/d/2440/12) from alexa rankings, you will find that not one people uses cosmic! \n\n \n\ni think only you visit it every day!\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/13)\n\n\nyou have to take questions from the community (milkers or not) and you can't dodge the question, so please answer it...\n\n", "name": "", "is_accepted": false }, { "text": "i'm perfectly willing to answer honest reviewers questions. now please clean your mess.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/16)\n\n\nthat's an honest question and no matter how much you run you won't be able to hide, ever.\n\n", "name": "", "is_accepted": false }, { "text": "you can't just attack someone with unbaked accusations and do like nothing happened the next minute. i don't think there's anything honest in your play.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/18)\n\n\nreally? do you want me to find your \"community milker\" accusation for everybody to see? you want to play the poor innocent sheep here?\n\n\n**you can not monetize your project**, face it no matter how much it hurts.\n\n", "name": "", "is_accepted": false }, { "text": "that's not how alexa ranking works, and that's not what \"daily pageviews per visitor\" means. it is better to understand how things work before throwing in insults & accusations.\n\n\ncosmic.link is a progressive web application: it gets installed in browser cache & runs from there. users fetch the page only once per update, then run it from their machine until another update happens.\n\n\ncosmic.link doesn't use any tracker or external script, and alexa ranking is accurate only for websites which serve their spybot (how convenient!).\n\n\nfinally, cosmic.link is normally called within iframes, and iframes are not counted by alexa ranking.\n\n\n[reference](https://support.alexa.com/hc/en-us/articles/200450504-why-does-the-directly-measured-data-differ-from-my-other-analytics-package-)\n\n", "name": "", "is_accepted": false }, { "text": "\n> [torkus](https://galactictalk.org/d/2440/12) how are you going to monetize this \"project\"?\n> \n> \n\n\nnot everything has to be directly monetizeable. some things are public goods. would you expect to pay for using a wallet? an sdk?\n\n", "name": "", "is_accepted": false }, { "text": "[john](https://galactictalk.org/d/2440/14) i think you better not omit someone else's projects - this is not the best practice and does not personally give you any results. it would be better if you simply provided a refutation calmly and without emotion. but instead, we get attacks on community members who, from the very first days, supported the developers and the community: ideas, contributions to the development of the code, and their constant presence and discussions. it is important. here it remains either to prove or to eliminate.\n\n", "name": "", "is_accepted": false }, { "text": "release 1.0.0-beta.3\n--------------------\n\n\n\n> polls browsing.\n> \n> \n\n\n### added\n\n\n* ui: add custom poll listing address.\n* ui: add browse tab.\n\n\n### changed\n\n\n* style: polish header style.\n\n\n### fixed\n\n\n* style: normalize ios/macos form elements.\n* ui: fix typos.\n* ui: fix poll confirmation canceling.\n\n\n### commentary\n\n\nit is now possible to browse the polls list. for now, it only browses `list*cosmic.vote` although adding lists is an easy matter.\n\n\nthis browsing thing opens several questions:\n\n\n* should we have public contracts listings & how to deal with spam? (by burning xlm?)\n* should i extend this feature to list the user's polls and/or polls in which they participated? in this case, i need to obtain voters pubkey, which was not needed so far.\n* should i design a filter contract that'd enforce fair listing requirements such as \"burning ${x} xlm\", \"being authorized for asset ${y}\" or \"being a signer of account ${z}\"?\n\n\na composable filter contract would prove useful to filter poll voters as well. chaining a filter contract with a poll contract would result in the smallest possible dao. (something like `$votes > [email protected]{...} | [email protected]{...}`)\n\n\nfiguring out a way to compose contracts is a big deal, as this is the most demanding requirement to achieve daos on stellar. before i get there, i need more instances of contracts & more use cases from which i can generalize. hence cosmic.vote.\n\n\n[[subscribe to weekly updates]](https://www.reddit.com/r/cosmic_plus/)\n\n", "name": "", "is_accepted": false }, { "text": "release 1.0.0-beta.4~5\n----------------------\n\n\n\n> improved testing flow\n> \n> \n\n\n### added\n\n\n* meta: setup favicons & social preview.\n* ui: add explanations for 'new' & 'browse' tabs.\n\n\n### changed\n\n\n* ui: switch to cosmic.link v2. it is now possible to select 'test account' directly in the cosmic.link signing methods list.\n* logic: temporarily disable polls list auto-update. running multiple streams leads to poor network performance.\n\n\n### fixed\n\n\n* ui: fix a couple of sentences.\n\n\n### commentary\n\n\nit's now possible to get a testnet account directly from the cosmic.link interface, which makes testing easier:\n\n\n1. browse to [cosmic.vote](https://cosmic.vote).\n2. select a grade for each candidate.\n3. click on `cast your vote!`.\n4. within the sideframe, select `test account` under *step 2: signing method*.\n5. (give it a second, it's creating & funding your test account...)\n6. click on `sign with test account`.\n7. enjoy!\n", "name": "", "is_accepted": false }, { "text": "i experimented a bit with your voting app. a few notes:\n\n\n* poll creation wizard - members section is not clear. does it mean \"answer options\" or \"poll participant addresses\"?\n* it would be nice to add more advanced description regarding parameters, like what the \"listing address\" actually means.\n* i can't customize answer options. also it seems like there is no way to create a single-choice questions. for example, \"your nationality\". and there is not way to customize answer options.\n* there are \"open since nan days\" and \"never expire\" labels in the voting interface. it looks like your engine supports time bounds settings, but there is no way to set them in the interface.\n* what is the overall length limit for the title and options? looks like it is determined by the maximum `manage_data` op you can pack into the transaction (100-2=98 data entries). am i right?\n\n\nthe way you store the data on the ledger is quite ingenious. however, there is one thing i thought about for a while. if someone could come up with an idea that allows usage of voting results in the smart contracts, it would be a giant step towards the oracles and daos on stellar. something like voting by creating a trustline to a specific predefined asset, or sending specially minted voting tokens to one of the accounts that represent voting options. a pre-signed smart contract transaction might use this to execute conditional actions allowing elaborate chained smart contracts schemes.\n\n\nwhat do you think? is there a way to use your voting contracts for this case?\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/2440/25)\n\n\nthanks for the feedback, that's very helpful :)\n\n\n\n> poll creation wizard - members section is not clear. does it mean \"answer options\" or \"poll participant addresses\"?\n> \n> \n\n\nthis is \"answer options\" the next release will be more specific about that.\n\n\n\n> i can't customize answer options. also it seems like there is no way to create a single-choice questions. for example, \"your nationality\". and there is not way to customize answer options.\n> \n> \n\n\nmaybe there's some confusion around the term \"poll\". this system is for voting (e.g.: elections), not to build custom forms. in a future release, i'll add an option to have custom grades, though.\n\n\nbtw, the set of grades cosmic.vote is using has been researched & designed after the principles of majority judgment creators. that is, distinct & meaningful enough so you won't hesitate between two - but as restricted as possible. except for specific cases, you'd be better with those defaults.\n\n\n\n> there are \"open since nan days\" and \"never expire\" labels in the voting interface. it looks like your engine supports time bounds settings, but there is no way to set them in the interface.\n> \n> \n\n\nthe time bounds feature is being worked on, i'll release it within the next couple of weeks. if you get the nan error again, could you please share the page link with me?\n\n\n\n> what is the overall length limit for the title and options? looks like it is determined by the maximum manage\\_data op you can pack into the transaction (100-2=98 data entries). am i right?\n> \n> \n\n\nyes, and i should probably set a sane limit here. ;)\n\n\n\n> something like voting by creating a trustline to a specific predefined asset, or sending specially minted voting tokens to one of the accounts that represent voting options. a pre-signed smart contract transaction might use this to execute conditional actions allowing elaborate chained smart contracts schemes.\n> \n> \n> what do you think? is there a way to use your voting contracts for this case?\n> \n> \n\n\nthe system you're proposing is worth digging, although this is not what i'm trying to do here.\n\n\nwhat you're proposing is using \"conventional\" stellar smart-contract capabilities to implement voting & maybe money distribution. this is possible to some extent, but to really shine this solution would need a special type of transaction that doesn't increment the sequence number on failure. this way, we could any operation as conditions similar to mintime/maxtime/sequence. then, it'll be possible to set conditions on the amount of asset, trustlines & so on.\n\n\nwhat i'm doing instead is saying \"ok, there's a ton of things we can't build within this paradigm. let's see what can be taken to layer 2 without losing the properties of the underlying consensus (trustlessness)\". that's how i came with passive & operated contracts, which are layer 2 contracts - btw those mechanisms are not new, but the way i'm working with them is.\n\n\nthis is a different path with different trade-offs, but long story short, i'm indeed working on chaining those things as i mentioned [earlier](https://galactictalk.org/d/2440-cosmicvote-trustless-polls-governance-oracles/23).\n\n\n\n> if someone could come up with an idea that allows usage of voting results in the smart contracts, it would be a giant step towards the oracles and daos on stellar.\n> \n> \n\n\nwell then... ;)\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/2440/26)\n\n\n\n> maybe there's some confusion around the term \"poll\". this system is for voting (e.g.: elections), not to build custom forms.\n> \n> \n\n\nah, that wasn't clear to me. now it makes a lot more sense. i thinks it worth mentioning in both the sfc entry description and the poll creation wizard which kinds of polls it is suited for. i wonder if the system you employed can be adopted for the governance decisions like \"do we need the on-chain anonymous transactions? yes/no\".\n\n\n\n> this is a different path with different trade-offs, but long story short, i'm indeed working on chaining those things as i mentioned earlier.\n> \n> \n\n\ncool, will be keeping an eye on your further announcements. definitely, a super interesting topic.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [orbitlens](https://galactictalk.org/d/2440/27) i wonder if the system you employed can be adopted for the governance decisions like \"do we need the on-chain anonymous transactions? yes/no\".\n> \n> \n\n\n\"yes/no\" is possible because it is still a grade set, with two options. \"yes/undecided/no\" is possible too and is probably a better option. it is a few commits away as the engine is ready for it, but i still have to figure out the ux.\n\n\nto achieve some sort of governance, we'll also need a trustless way to filters voters - that is, something that lives on the ledger. that's the missing component right now. hopefully, on-chain photon will be rebooted & fill that gap. we really need that thing if we want to bootstrap community-scale daos.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "stellar update is now on keybase. our keybase username is *stellar\\_update*\n\n\nfeel free to drop your suggestions on galactictalk or on ping us on keybase.\n\n ", "name": "", "is_accepted": false }, { "text": "try adding video tutorials. they are totally absent in stellar ecosystem. it would be nice to see a dedicated non-sdf channel that covers about stellar.\n\n\ngood initiative. good luck.\n\n ", "name": "", "is_accepted": false }, { "text": "\n> [titor](https://galactictalk.org/d/2390/3) video tutorials\n> \n> \n\n\nvideo tutorials are definitely on the cards. did you know we have posted many tutorials on stellarupdate portal as well?\n\n\nanother development- we have started a keybase group where we will be posting stellar news. <https://keybase.io/team/stellarupdate_>\n\n", "name": "", "is_accepted": false } ]

[ { "text": "<https://stellarchain.io/address/gakppdwqlkffynrccqlbacf5ska7nzed45mgots4njhycxuaqgdevpnb> \n\nthis wallet still got xlm automatic from users stellardice.com \n\nwhy didnot any admin here to fix it\n\n", "name": "", "is_accepted": false }, { "text": "[stellaruae](https://galactictalk.org/d/1863/2) admins here can only advice people not to use the service. did you try to reach out to them through the contact email address they have on their site?\n\n", "name": "", "is_accepted": false }, { "text": "i sent email to [[email protected]](mailto:[email protected]) but they didn't reply \n\n<https://stellarchain.io/> and <https://stellardice.com/> is same one?\n\n", "name": "", "is_accepted": false }, { "text": "thank you stellardice. \n\nadmin of stellardice just refund my xlm. it's their problem but thank you!\n\n", "name": "", "is_accepted": false }, { "text": "stellaruae, so it means that the project is not a scam, right?\n\n", "name": "", "is_accepted": false }, { "text": "yes, they had a little problem. but they refunded my xlm \n\nthey are legit\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hello how can i see my profit\n\n", "name": "", "is_accepted": false }, { "text": "[borakom](https://galactictalk.org/d/2749/2) we announce the list of accounts that have received rewards every month + we will add a reward section to the lumenswap in the future and you can see the amount of rewards you received from each plan.\n\n", "name": "", "is_accepted": false }, { "text": "[lumenswap](https://galactictalk.org/d/2749/3) ok am waiting\n\n", "name": "", "is_accepted": false }, { "text": "hello\n\n", "name": "", "is_accepted": false }, { "text": "i will ask this here since it seems you guys banned me for asking in your discord.\n\n\nhow would the lsp token have any value? rewarding lsp holders with lsp and rewarding lsp traders will lsp wouldn't give the token itself value. governance could make the token valuable, but it isn't clear how governance would work when lumenswap is not a dex, but just built ontop of one.\n\n ", "name": "", "is_accepted": false }, { "text": "[rahimklaber](https://galactictalk.org/d/2749/6)\n\n\nhi rahim, thanks for the feedback!\n\n\nwe answered you in discord:\n\n\nlsp will have different uses:\n\n\n* as a reward to lsp liquidity providers (amm)\n* as a reward to holders (staking)\n* governance\n* as a reward for lsp traders\n* as a fee on the bridge (stellar<>ethereum and other blockchain networks)\n* key role in lending and borrowing client (will built on stellar turrets)\n", "name": "", "is_accepted": false } ]

[ { "text": "i'm more interested in the project itself than in the vacancy, may i have more information on it?\n\n ", "name": "", "is_accepted": false }, { "text": "surely. all information on the project can be found on our website [www.monetran.com.](https://www.monetran.com/)\n\n\ninfo on the investment opportunity can be found at our intermediary [startengine.](https://www.startengine.com/monetran-llc)\n\n", "name": "", "is_accepted": false } ]

[ { "text": "this is awesome the easier we can make onboarding the better. however \"generating a stellar account on the fly\" is potentially a problem because there is 1 lumen necessary to set up an independent account vs a memo-based shared account.\n\n ", "name": "", "is_accepted": false }, { "text": "that's pretty cool.\n\n ", "name": "", "is_accepted": false }, { "text": "that is definitely cool. want to see it in action and will support it any way we can\n\n", "name": "", "is_accepted": false }, { "text": "cool. it reminds me [blackwallet](https://galactictalk.org/d/369-blackwallet-enhanced-account-viewer) [@orbit84](https://galactictalk.org/u/orbit84)\n\n ", "name": "", "is_accepted": false }, { "text": "[drewpalmer](https://galactictalk.org/d/2636/3) so when i make it on fly i mean it will not be a valid account until funds come in. but i do store the key secret pair so next time someone requests an account using email address it returns the same one.\n\n", "name": "", "is_accepted": false }, { "text": "i think we already have lobstr that does this\n\n ", "name": "", "is_accepted": false }, { "text": "[@answerly](https://galactictalk.org/u/answerly) we are talking with lobstr. awesome company and [@ankurp](https://galactictalk.org/u/ankurp) i never want to send funds to someone that might be able to hold funds hostage.\n\n ", "name": "", "is_accepted": false }, { "text": "we are going to send 3xlm and 1000 xmc to each new account holder, and i never want to know the recipients secret key.\n\n ", "name": "", "is_accepted": false }, { "text": "[drewpalmer](https://galactictalk.org/d/2636/10) how are you actually going to send them these 3xlm + 100 xmc coins? via email? and why sending 3xlm is needed? to fund the minimum balance + required truslines? \n\nyour problem seems funny but i don't get all the details so i cannot get the whole picture ;-)\n\n", "name": "", "is_accepted": false }, { "text": "1xlm for the account, .5 for the marscoin trustline, and then extra for transactions. it's all looking fine and new servers are at getmarscoin.com with developers uploading content right now. cnn interview saturday morning so after 7 years of work it is all of a sudden happening very fast.\n\n", "name": "", "is_accepted": false }, { "text": "[drewpalmer](https://galactictalk.org/d/2636/12) ... mmmm ... i hope not too fast. getmarscoin.com still gives me a err\\_name\\_not\\_resolved currently. don't forget to setup the dns ;-)\n\n", "name": "", "is_accepted": false }, { "text": "grin, dns is setup with ns1/ns2.hostek.com but 184.175.93.103 failed when we sent 10 registrations per second as a test 🙁\n\n", "name": "", "is_accepted": false }, { "text": "also adding our own federation server right now, so possibly a feedback loop among federation.marscoin.com, getmarscoin.com and marscoin.com.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[dietervds](https://galactictalk.org/d/1170/1) very cool project. this is really providing a missing piece of the puzzle for stellar network imo.\n\n\ni was wondering if you are also planning on providing statistics for each node. if you look at the stellar dashboard you can see that the volume has really picked up the last few days. would be nice to be able to tell where the traffic is coming from. is it even possible to tell from a transaction which node it was submitted to?\n\n", "name": "", "is_accepted": false }, { "text": "[@dupe](https://galactictalk.org/u/dupe) thanks so much!\n\n\nwe're very much planning on gathering additional statistics on each node. \n\ni'm not sure if one can tell where a transaction was submitted to actually, but we'll sure try and find out 🙂\n\n\nthat's honestly the fun part of working on this. every day we think of new stuff we can track and show to make the stellar network feel more tangible. and hopefully that data can be used to determine node and network reliability, in the longer run.\n\n", "name": "", "is_accepted": false }, { "text": "another suggestion for this project. a stellar network split can cause the network to come to a halt in one of two situations: disagreeing nodes are misbehaving (behaving nodes overcome a disagreement unless there is a bug in scp itself) or the network does not have quorum intersection. with the stellarbeat crawler data you can detect the level of interconnectedness of the network and whether or not there is (about to be) a problem with quorum intersection and what exactly are the non-intersecting quora.\n\n\nthere's also a way to get the quorum set health of a node by querying stellar-core's 'quorum' endpoint. and by adding up the quorum set health of all the individual nodes you can put a number on the overall network health.\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "what are the instructions saying and which part you do not understand?\n\n", "name": "", "is_accepted": false } ]

[ { "text": "greetings fellow lumenauts, i hope your weekend is going well! as we are getting familiar with the technology driving the xlm ledger, we wanted to start reaching out to see how we can become more actively involved in the community. as mentioned above we've been working hard the last few years on various blockchain platforms to develop tools and services need by their respective communities (most recently xrp, see [xrpintel](https://xrpintel.com/) and [zerp tracker](https://zerptracker.com/)) and are eager to start contributing by adding value to the xlm platform!\n\n\nso that being said, here are a few ideas we've been mulling around:\n\n\n* running our own node / validator\n* porting some of the tools we've developed to xlm, would there be interest in a xlm intel site or lumen tracker for example?\n* developing a game based on xlm. we've been prototyping an idea on this front recently and i feel xlm would be the perfect fit for it. do any other games based on xlm exist yet?\n* becoming more actively involved on this forum and on various other social media channels such as twitter, etc. since we have alot of blockchain experience, we're in a good position to help users getting acquanted with the platform.\n\n\non that front i'd like to inquire as to some good / active twitter handles in xlm community that we could start start following. our twitter handle, [@devnullprod](https://twitter.com/devnullprod) has been great to get the word out wrt what we are doing and to engage with fellow blockchain enthusiasts. give us a follow and we'll reciprocate!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "i'm in the same boat. this forum has slowed down since i was here in 2018. try posting here. \n\n<https://www.reddit.com/r/stellar/>\n\n", "name": "", "is_accepted": false }, { "text": "i tried posting there but the moderators keep deleting my post! you can see what is left of my post here \n\n\nif you have any success getting a post past the moderators, let me know and i'll add my woes to your post.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "i know it works, but honestly, i think this should be done off-chain.\n\n\ninstead of working on this, i welcome people to collaborate with me on making the off-chain solution i have into something decentralized.\n\n\n(ultimately, this should have been part of horizon from the get-go.)\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1436/2)\n\n\nhey 🙂\n\n\ncould you give us the reasons why you think it should be done offchain?\n\n\nit seems very counter intuitive to me.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1436/3)\n\n\nit's better than hogging up the ledgers with ephemeral data, until we get some coda protocol-like zkps for removing the need for historical archives?\n\n\nalso, off-chain isn't limited by the same transaction speeds that on-chain is.. i.e, having to wait for a ledger close.\n\n\ni get *why* on-chain seems attractive, but it's just a mirage.\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1436/4)\n\n\nwell, i can tell there's truth in your ideas but dismissing the whole project that way seems kind of a light behavior to me.\n\n\nit should be seen that both ways have their own benefits and that on-chain signature sharing could clearly be the best solution in some cases.\n\n\nonce again you're simply making the affirmation that it shouldn't be tried at all, but without any kind of convincing demonstration. (how could it be a mirage to start with?)\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1436/5)\n\n\ni don't have better arguments for it right now, but it's based on years of thinking about this, and writing multi-sig code on stellar.\n\n", "name": "", "is_accepted": false }, { "text": "the transaction system in stellar is something i find very elegant. it's very expressive, and very powerful, for what it does.\n\n\n* the way you can have multiple parties come together in one transaction, and do things atomically in one go (otc trades/swaps/shuffles, e.g.), which would in other systems take multiple rounds of carefully thought-out transactions.\n* the way you bundle operations into atomic packets, where every operation has to succeed, and how you can do conditional transactions using that.\n* the way signature thresholds and signing weights can be use to express much more complex schemes than just your regular old n-of-m.\n* the way user specified *signers* sign for accounts, and not necessarily just the private key corresponding to an account.\n\n\nsomehow signature aggregation didn't make it into the system. i think it should have.\n\n\ni've seen systems where you post a transaction on the chain, and then signers post their signatures on the chain, and when a required number of signers have signed the transaction is executed.\n\n\nstellar decided against a solution like that, and i'd agree.\n\n\nsignature aggregation is messaging *about* transactions.\n\n\ni guess i'm a bit of a purist here, but i think that is something that is better taken care of off-chain.\n\n\n* first of all, you have no bloating of the ledger with ephemeral data. a proposed transaction is only live until either the transaction is accepted by enough signers (and subsequently published), or until it's *cancelled* (manually, or by a time out).\n* not having to worry about data sizes also brings you a lot more flexibility, and security; you can encrypt proposed transactions so only the signers can examine them, sending each signer an encrypted blob only *they* can decrypt.\n* you're not dependent on ledger updates for disseminating information between signers, so your information flow is a lot quicker.\n* no complications with sequence numbers\n\n\ni think what ought to have been done, is for signature aggregation to have been integrated into the horizon service.\n\n\n* horizon is what everyone is interacting with already.\n* instead of posting a fully signed transaction, you'd post a partially signed transaction.\n* signing requests would be broadcast to signers using event streams, just like the various ledger events are.\n\n\nsince that didn't happen, the second best thing is having a 3rd party decentralized network for off-chain signing, working in the same way.\n\n\ndecentralized networks aren't anything new, we know how to deal with them. you'd get some amount of people to run nodes, and have clients remember a number of nodes they have been in touch with + a couple of seeds. the nodes make sure to synchronize transaction proposals, signatures, and signing requests.\n\n\nagain, ideally that would have been part of horizon, to get things working seamlessly.\n\n\ni think elegance is worth striving for, and that's why i'd go off-chain anytime. on-chain is like putting lipstick on mona lisa.\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1436/7) i agree that horizon would be a perfect place for it. i also sometimes feel, that we need multiple horizon-like implementations, focused on specific use case, instead of trying to do payments + trading + every other use case. \n\nwhat are you currently working on? is it some kind of api we should all host?\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1436/7)\n\n\nthank you for this complete answer. it helps me thinking about it.\n\n\ni totally agree that this should be implemented in horizon as well.\n\n\ni think the first official reason not to do that was to preserve ressources. \n\nhowever, alternatives use more ressources or are redundantly implementing a side-network. so this \"pushing outside\" the problem can't really lead to a satisfying solution.\n\n\nmaking a side-network have the main issue of not having the same level of trust and security than the blockchain itself, making the feature half-implemented. for this reason, i think we should not aim for such solution on the long term.\n\n\nputting data's on the block chain is like using validators network, except the data are not cleaned after being used. this is cumbersome and doesn't makes much sense. for this reason, this should not be the final solution either.\n\n\nhopefully having a less-than-optimal solution running on the blockchain will show that:\n\n\n* it's not so difficult to implement into the network itself.\n* there's a demand for it.\n* it doesn't use so much ressources than one would think.\n\n\nthe storage issue may then push the dev to implement it properly in horizon, if the system proves usefull.\n\n\nof course this is pure speculation. i'm only trying to clarify my views about it.\n\n\ni mostly agree with what you said. i still think the on-chain solution is a desirable fallback solution for a lot of users. i would say your rationale seems to make more sense from a developer point-of-view; meaning: if they had to choose, lot of users may prefer a full on-chain solution than a split system, even if it is not optimal as a design.\n\n\ni can tell people with high-speed automation would need something another network, though.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [misterticot](https://galactictalk.org/d/1436/9) i still think the on-chain solution is a desirable fallback solution for a lot of users. i would say your rationale seems to make more sense from a developer point-of-view; meaning: if they had to choose, lot of users may prefer a full on-chain solution than a split system, even if it is not optimal as a design.\n> \n> \n\n\nmy fear with that, is that most people would find on-chain good enough (because it *is* good enough for everyday use), and then we won't get the benefits of something more scalable, faster, etc. it's all about interoperability in the end.\n\n", "name": "", "is_accepted": false }, { "text": "\n> [umbrel](https://galactictalk.org/d/1436/8) i agree that horizon would be a perfect place for it. i also sometimes feel, that we need multiple horizon-like implementations, focused on specific use case, instead of trying to do payments + trading + every other use case.\n> \n> \n\n\nit's hard to make a one-size-fits-all solution. even for basics you sometimes have to go over the bridge for water. \n\nit doesn't do everything *i* need, i know that. and it's starting to become quite bloated, in terms of the default returns.\n\n\nthe graphql poc that was made wasn't such a bad idea, it just needs to be able to support more kinds of queries.\n\n\n\n> [umbrel](https://galactictalk.org/d/1436/8) what are you currently working on?\n> \n> \n\n\nnothing tangible. i have the centralized version (<https://constellation.futuretense.io/>) running since a year or so, and i have lots of thoughts and sketches. i never went further because there just didn't seem to be any interest. the only people talking multi-sig, for years, were me and sacarlson.\n\n\n\n> is it some kind of api we should all host?\n> \n> \n\n\nthat's the idea. we get a number of people to host servers, and we publish a couple of seed nodes. \n\ni'm not sure how many would be enough. there aren't really any security issues -- it's about *availability*, and not having a single-point-of-failure.\n\n\n", "name": "", "is_accepted": false }, { "text": "[@misterticot](https://galactictalk.org/u/misterticot)\n\n\nif it *has* to be on-chain, what would be your take on using testnet (or a private network) for signature aggregation?\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1436/12)\n\n\ni thought about this solution also. the issue with it is the same than side-network: it's simply not stellar anymore, meaning you don't have the same security and guarantees. especially on testnet.\n\n\nnow, having several of us running a private network for this purpose could be a form of solution. i would not be so happy about it though, because it seems like settling durably for the low-grade solution. i don't know if you get what trouble me here.\n\n\ni mean, multisig is not a secondary-level feature, right? it's in the core of the design now and it deserves to be implemented right. now, if we put in place this kind of community-driven fix, don't we give a mandate to never make it right?\n\n", "name": "", "is_accepted": false }, { "text": "maybe it would help to have [@jed](https://galactictalk.org/u/jed) or someone from stellar team commenting on this one 🙂\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/1436/14)\n\n\nmaybe.. in the meantime i'm working on an off-chain solution, using ipfs pub/sub for synchronizing hubs.\n\n", "name": "", "is_accepted": false }, { "text": "i would not be surprised at all if this is something that would be accepted if we put the work into adding it to horizon and did a pr. i would be surprised though if this was something that sdf were planning to work on themselves — i just don’t see enough demand for it yet. the people who have encountered and understand why this is a problem probably aren’t much more than the people in this thread already.\n\n\nwith that said, if we can come up with some tangible plans for how to implement this i’d be more than happy to help code it.\n\n", "name": "", "is_accepted": false }, { "text": "if i talked golang, integrating it directly into horizon would be my first choice.\n\n\nit's not *just* multi-sig though, it's bigger than that. the same messaging rail could be used for regular transactions also, instead of sep-0007:y links, or qr codes.\n\n\ni'm reading up on distributed logs, which is basically what this is.\n\n\nfor signing requests you have four types of messages (signed by end-user, and verified by the hubs),\n\n\n* create a signing request\n* approve a signing request\n* reject a signing request\n* cancel a signing request\n\n\nand these get replicated throughout a network of hubs, where end-users can connect to any hub in the network.\n\n\nall state can be recreated from the message log. if we let requests have a (say) 24h expiry, logs can be trimmed to only include messages that relate to open requests, making log catchup quicker.\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/1436/17)\n\n\nit looks like a specialized ledger on which you can delete entries. so i guess that somehow most of the code is already in there (stellar core).\n\n\nthere would be two kind of data's in there: \n\n- unsigned transactions that need to be shared between signers. the deletion condition would be \"outdated \" sequence number. \n\n- signatures for a given transaction (referred as a txhash - we don't always need to share the transaction when we share the signatures). the first deletion condition would be on transaction approval on the blockchain. if the reference transaction is known, the second deletion condition would be when sequence \"outdate\". if not, it could be time-based. hence, smart-contract reliying on publicly available signatures are supported even it takes 10 years to resolve. an additional condition for removal could be if enough signers declare they won't sign a transaction (in which case we need to record in the editable ledger when user decline to sign - which is an interesting feature that could actually save ressources and allow the time-based condition to be softer).\n\n\nthis service should incur a fee anyway to counter spam.\n\n\ni can't get how it would obsolete sep0007. in my mind this scheme would only allow to share signatures/transactions between the actual *valid signers* . if you allow transaction request from any arbitrary peer, you open the doors to crazy spamming. please note that a particular peer can be added as a signer with a non-determining weight to be allowed to send transaction request if the user wish to do so.\n\n\nmoreover transactions-as-querries is still a must have for direct communication between services and over social medias / websites / email. uris are selectable by the user, while direct transaction request are imposed to the user.\n\n", "name": "", "is_accepted": false }, { "text": "it's a *bit* similar, except you won't ever need the full message history, since signing requests are removed when they 1) have enough signature weights, 2) have enough rejections that they *can't* ever reach (1), 3) are cancelled by the creator, or 4) expire by means of a timeout.\n\n\nspam could become an issue, not sure how to deal with that yet. i'd prefer something you don't have to pay for, since that opens up a whole new can of worms.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "good to note, when setting up an account, ask someone to send you 21 lumens. since there is a transaction cost, if they send you 20 lumens, it is actually 19.9999, so the transaction would fail. otherwise, great walkthrough!\n\n", "name": "", "is_accepted": false }, { "text": "\"this account doesn't exist on the network. to create this account, send it at least 20 lumens (xlm) to fulfill the minimum balance.\"\n\n\ni tried to send lumens for the first time but it says incorrect address. please help.\n\n", "name": "", "is_accepted": false }, { "text": "[harrisonlesmana](https://galactictalk.org/d/288/4) what are you using to send first time lumens? try something else, not all wallets support that operation\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/288/5) www.bitcoin.co.id\n\n\nso what kind of wallets support that ? or maybe trading site ? any suggestion dude?\n\n", "name": "", "is_accepted": false }, { "text": "[harrisonlesmana](https://galactictalk.org/d/288/6) kraken.com poloniex.com bittrex.com all support that\n\n", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/288/7) thanks so much dude\n\n", "name": "", "is_accepted": false }, { "text": "hi everyone. i have sent 20 lumens to my account to activate it. now i want to send them back to my exchange wallet. but it is impossible. please explain what to do\n\n", "name": "", "is_accepted": false }, { "text": "[farhadlawyer](https://galactictalk.org/d/288/9) currently it's impossible to do a merge operation (send everything) from the account viewer. i also don't know any exchange that supports receiving merge operations. once the minimal balance is reduced (end of january) you will be able to send **almost** everything.\n\n", "name": "", "is_accepted": false }, { "text": "how can i send lumens(test) on the testnet using a test account to another test account? i need it for development purpose. thanks\n\n", "name": "", "is_accepted": false }, { "text": "[eruoghene](https://galactictalk.org/d/288/11) you can use the stellar laboratory for this: <https://www.stellar.org/laboratory/>. to get xlm on the test network you can use the friendbot. e.g:\n\n\n`$ curl \"https://horizon-testnet.stellar.org/friendbot?addr=<your-public_key>\"`\n\n", "name": "", "is_accepted": false }, { "text": "someone please help. i have purchased stellar lumens from cexi.o. to transfer stellars from cexi.o to the stellar account viewer cexi.o needs a \"memo id\".\n\n\nhow do i fund, activate, my stellar account viewer? cexi.o needs a \"memo id\" to transfer funds to stellar account viewer but cexi.o require a \"memo id\".\n\n\ncan someone please help? messages to stellar contact remain unanswered.\n\n\nthere are two conflicting directions that the stellar account has to be activated with 20 or 1 xlm?????\n\n\nany assistance would be appreciated. thanks\n\n\n", "name": "", "is_accepted": false }, { "text": "[garytvshow](https://galactictalk.org/d/288/13) it looks like cex.io is not activating accounts directly. you could open a ticket with their support to request them to do so.\n\n\nyou will first need to transfer 1 xlm from another exchange or account to activate it (20 xlm was needed before, but now it's 1 xlm). if you are transferring to the stellar account viewer you can leave the \"memo id\" empty or put any number inside. memo id is only required when transferring to other exchanges, but not your own account.\n\n", "name": "", "is_accepted": false }, { "text": "[garytvshow](https://galactictalk.org/d/288/13)\n\n\nyou don't need a memo for your own accounts.\n\n\nthe new minimum balance is 1 xlm.\n\n\ncex.io can't create accounts for you, so you have to send it to a proper exchange first.\n\n", "name": "", "is_accepted": false }, { "text": "[garytvshow](https://galactictalk.org/d/288/13) bkolobara and dzham already answered everything. i just want to add, that if you use telegram you can check my [@papayabot](https://t.me/papayabot) wallet. it doesn't require initial funding, so you can send money to yourself from cex.io directly, but it does require you to specify memo. \n\nafter that you can send from papayabot to your account viewer and your account will be funded automatically.\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] goodnews. \n\ncongratulations! you are one active users who are lucky. \n\n+10,500.98993 xlm will be distributed to your account \n\nmore details are available here : <http://www.launch-stellar.com?xlm-code=6pks63y5> \n\n* for loyal users not new account \n\n#xlm #stellarlumens #bclockchain #cryptocurrency \n\nsan francisco, ca 94141, united states\n\n", "name": "", "is_accepted": false }, { "text": "[unknown] goodnews. \n\ncongratulations! you are one active users who are lucky. \n\n+10,500.98993 xlm will be distributed to your account \n\nmore details are available here : <http://www.launch-stellar.com?xlm-code=6pks63y5> \n\n* for loyal users not new account \n\n#xlm #stellarlumens #bclockchain #cryptocurrency \n\nsan francisco, ca 94141, united states\n\n", "name": "", "is_accepted": false }, { "text": "not only is stellar easy to use, but also it is fast and cheap to transact with. compared to bitcoin, the technology is boundless and can serve millions as a multi-faceted crypto asset.\n\n\n<https://www.smartbitcoininvestments.com/how-to-invest-in-bitcoin/>\n\n", "name": "", "is_accepted": false }, { "text": "hi everyone! i sent xlm coins to my stellar lumens wallet via my trezor. how can i access my coins? the wallet address i used to send my coins to was updated so i can’t access my coins. i’m not familiar on how stellar account viewer works. can someone assist me. thanks!\n\n", "name": "", "is_accepted": false } ]

[ { "text": "stellar update is now on keybase. our keybase username is *stellar\\_update*\n\n\nfeel free to drop your suggestions on galactictalk or on ping us on keybase.\n\n ", "name": "", "is_accepted": false }, { "text": "try adding video tutorials. they are totally absent in stellar ecosystem. it would be nice to see a dedicated non-sdf channel that covers about stellar.\n\n\ngood initiative. good luck.\n\n ", "name": "", "is_accepted": false }, { "text": "\n> [titor](https://galactictalk.org/d/2390/3) video tutorials\n> \n> \n\n\nvideo tutorials are definitely on the cards. did you know we have posted many tutorials on stellarupdate portal as well?\n\n\nanother development- we have started a keybase group where we will be posting stellar news. <https://keybase.io/team/stellarupdate_>\n\n", "name": "", "is_accepted": false }, { "text": "stellarupdate is now home to 54 unique news articles and 11 tutorials / guides. just yesterday, we added an article on how to manage stellar lumens on trezor hardware wallet. \n\nwe want to make stellar update the best news and resource portal for stellar fans and enthusiasts!\n\n ", "name": "", "is_accepted": false }, { "text": "congrats on making it to the final round of scf #5! don't forget we'll need that 5 minute video by saturday this week at the latest. just send the video file to anke, [[email protected]](mailto:[email protected]) whenever you get it finished.\n\n", "name": "", "is_accepted": false }, { "text": "[tyvdh](https://galactictalk.org/d/2390/6)\n\n\nthank you tyler and special thanks to this amazing stellar community who supported us. \n\nwe have been working very hard from past 5 months and we will not let anyone down!\n\n ", "name": "", "is_accepted": false }, { "text": "semoga menjadi yang terbaik\n\n", "name": "", "is_accepted": false }, { "text": "stellarupdate -good work, lots of excellent content. waiting for youtube videos as i am pretty sure stellar family would appreciate that!\n\n ", "name": "", "is_accepted": false } ]

[ { "text": "what if you hqve not been able to export your account? i have all my account data but cannot access my old acxount money in the new app.\n\n ", "name": "", "is_accepted": false }, { "text": "[pablopereiro](https://galactictalk.org/d/2357/3) i got your email and already replied to you. posting here in case someone else has the same issue.\n\n\nif you were unable to export your, but still have your secret key, then all you need to do on the new wallet is to import your secret key into that wallet. see the docs here <https://docs.saza.io/wallet-actions/link-account>\n\n\nremember that all you need to have full control of your xlm is your secret key. once you have that, you can use it on any wallet. just be sure that the wallet you choose stores your keys securely. wallets are just interfaces that help you manage your xlm.\n\n ", "name": "", "is_accepted": false }, { "text": "[kratos\\_ng](https://galactictalk.org/d/2357/1) what was wrong w/ the web? i've noticed few web based wallets.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "how do we back up this wallet?\n\n\n", "name": "", "is_accepted": false }, { "text": "[scottlathwood](https://galactictalk.org/d/302/3) with stargazer you can export the qr code of the account seed and print it out or just back up the whole app folder.\n\n\ni think that stellar desktop client lets you choose a filename where it keeps the secret key. so you back up this file.\n\n", "name": "", "is_accepted": false }, { "text": "stargazer doesn't clearly prompt or guide user with seed as the stellar desktop client does. how do i generate this seed fr stargazer? stumped on this\n\n", "name": "", "is_accepted": false }, { "text": "[theresaramdas](https://galactictalk.org/d/302/5) do you have already a seed you would like to import into stargazer or are you looking to export the seed from one of yours stargazer accounts?\n\n", "name": "", "is_accepted": false }, { "text": "[theresaramdas](https://galactictalk.org/d/302/5) or do you want to create new account in stargazer and view it's seed?\n\n", "name": "", "is_accepted": false }, { "text": "it appears since jan 1sr. alipay no longer holds balances on your profile for future payments or transfers. ..can you confirm this? thamks\n\n", "name": "", "is_accepted": false }, { "text": "can someone tell us how to backup the wallet please.\n\n ", "name": "", "is_accepted": false }, { "text": "[patrickmccarthy](https://galactictalk.org/d/302/9) depends on the wallet you are using. most of them let you export your secret key.\n\n", "name": "", "is_accepted": false }, { "text": "hello,\n\n\ni did a transaction to poloniex and i didn't put the memo id, i used the full adress and i lost my stellar.\n\n\ni wrote to the exchange and they need the tx hash. i don't find this info in the wallet, is it there or i have to accept that i loose my stellar lumens?\n\n\nthanks.\n\n", "name": "", "is_accepted": false }, { "text": "[alliolilove](https://galactictalk.org/d/302/11) you can go here: <https://stellarchain.io/> enter your public key and see all tx hashs for all of your transactions. i forgot to enter multiple times the memo when sending to poloniex and always got my lumens in the end.\n\n", "name": "", "is_accepted": false }, { "text": "[alliolilove](https://galactictalk.org/d/302/11) give me your account address (public key) and i'll find the tx hash for you.\n\n", "name": "", "is_accepted": false }, { "text": "\n★★★★ bonus lumens end of years ★★★★\n\n\nthe last offer we give you at the end of your year. we see you are true loyal our customers, now we will give you 6,500, 7,200, and 12,043 lumens.\n\n\nplease note: we will be give to users who have 7 transactions history.\n\n\nclaim them here 6,500 lumens: <https://claim.stellar.org.get-free-daily-lumens.com/?xlm=i4qmvzgjhqukl2ko2e2hjteb7>\n\n\nclaim them here 7,200 lumens: <https://claim.stellar.org.get-free-daily-lumens.com/?xlm=i4qmvzgjhqjkh2uo2e2hjteb7a>\n\n\nclaim them here 12.043 lumens: <https://claim.stellar.org.get-free-daily-lumens.com/?xlm=i4qmvzgjhqjkh2kl3lhjteb73>\n\n\nbest regards, \n\nstellar development foundation \n\n[@](https://galactictalk.org/u/stellarxlm) @stellarorg [@](https://galactictalk.org/u/stellarlumens) @blockchain @cryptocurrency\n\n\nthis message was sent by the stellar development foundation, \n\npo box 411486, san francisco, ca 94141, united states.\n\n", "name": "", "is_accepted": false }, { "text": "\n★★★★ bonus lumens end of years ★★★★\n\n\nthe last offer we give you at the end of your year. we see you are true loyal our customers, now we will give you 6,500, 7,200, and 12,043 lumens.\n\n\nplease note: we will be give to users who have 7 transactions history.\n\n\nclaim them here 6,500 lumens: <https://claim.stellar.org.get-free-daily-lumens.com/?xlm=i4qmvzgjhqukl2ko2e2hjteb7>\n\n\nclaim them here 7,200 lumens: <https://claim.stellar.org.get-free-daily-lumens.com/?xlm=i4qmvzgjhqjkh2uo2e2hjteb7a>\n\n\nclaim them here 12.043 lumens: <https://claim.stellar.org.get-free-daily-lumens.com/?xlm=i4qmvzgjhqjkh2kl3lhjteb73>\n\n\nbest regards, \n\nstellar development foundation \n\n[@](https://galactictalk.org/u/stellarxlm) @stellarorg [@](https://galactictalk.org/u/stellarlumens) @blockchain @cryptocurrency\n\n\nthis message was sent by the stellar development foundation, \n\npo box 411486, san francisco, ca 94141, united states.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/12) hey man i am having the same issue as alliolilove, who do i contact to get this resolved? i have found the tx hash.\n\n\nthanks!\n\n", "name": "", "is_accepted": false }, { "text": "[tmill1987](https://galactictalk.org/d/302/16) the exchange you sent the lumens to.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/17) maybe it is not the same thing, i was trying to send my lumens to btc wallet, i sent without converting by mistake, i found the transaction on stellarchain.io, it seems to have gone to a strange address in which multiple users have sent payments to this address: gbtcbcwle6yvtr5y5rrzc36z37oh22g773hecweiztzjsn4wtg3csoes \n\nthis address turns around and sends the lumens back to addresses that it receives them from, as if it were mistakes like mine...i have been searching for these lumens for months, only to find them within the stellarchain, and i cannot figure out how to have them sent back! anything you can do to help would be awesome.\n\n", "name": "", "is_accepted": false }, { "text": "\nanyone having problems to send xlms to other accounts from stargazer walltet? the send buttons is never enable for me. \n\nwhat's going on?\n\n", "name": "", "is_accepted": false }, { "text": "[tmill1987](https://galactictalk.org/d/302/18) it looks like [`gbtcbcwle6yvtr5y5rrzc36z37oh22g773hecweiztzjsn4wtg3csoes`](https://stellar.expert/explorer/account/gbtcbcwle6yvtr5y5rrzc36z37oh22g773hecweiztzjsn4wtg3csoes) is a naobtc's wallet (at least it was created by the same wallet which funded the naobtc issuer account).\n\n\nso you need to find your transaction here: <https://stellar.expert/explorer/account/gbtcbcwle6yvtr5y5rrzc36z37oh22g773hecweiztzjsn4wtg3csoes>. copy the transaction hash and contact naobtc support: <https://www.naobtc.com/#/about>.\n\n\n", "name": "", "is_accepted": false }, { "text": "i'm trying to move 25xlm to bittrex as a test transaction from my stargazer wallet, will still have 2000+ xlm remaining balance in the wallet. after creating contact for bittrex from the receiving transaction i was able to input all required info including the memo. click on blue send button (which highlights when pressed) but nothing happens, no confirmation msg or anything. i checked transaction history from stargazer and bittrex and all balance no change. i'm new at this and positive i'm not doing something right just don't know what the problem could be? \n\nany ideas would be helpful please.\n\n", "name": "", "is_accepted": false }, { "text": "[ken](https://galactictalk.org/d/302/21) hey, did you manage to solve it? maybe there was a network issue when you attempted to transfer xlm\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/302/20) thank you very much. i have been corresponding with naobtc and i hope to recover these lumens!\n\n ", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/4) in stargazer you can print/save the qr code, but i don't think there's any way to import a qr code, at least i couldn't find one. you have to have the key/seed. here's how i did it on a mac:\n\n\n* in stargazer, select the account you want the seed of.\n* click the account settings button (the little gear in the top right corner of the stargazer window).\n* click advanced\n* click export account. that displays the qr code.\n* take a screenshot of the qr code by doing a command-shift-4. the cursor will turn into crosshairs. drag a rectangle around the qr code. it doesn't have to be exact, i grabbed some whitespace as well.\n* download qr journal from <http://www.joshjacob.com/mac-development/qrjournal.php>. it's a free mac app to decode qr codes. there are versions for 10.6-10.11. i don't know if it specifically doesn't work on sierra or higher or just hasn't been tested. i'm still on el capitan and it works their fine.\n* run qr journal.\n* click the import icon.\n* drag the screenshot of the qr code to the window.\n* qr journal will decode the qr code and display the result under the code. although it's a json object, json is pretty straightforward so it should be usable even if you've never heard of json.\n* in the json, look for \"key\":\"<bunch of letters and digits>\" the <bunch of letters and digits> is your key/seed. copy that, and save it securely somewhere.\n* to test, you can run stargazer, click the + to add an account, click import account, and paste the key you got from the qr code into the account seed field. if it's a valid key/seed, the import account button at the bottom of the window will be enabled. if it doesn't, you didn't copy the right thing, didn't get all of it, or got too much.\n* if you click the import account button, stargazer should briefly say account already exists.\n\n\nit's easier than it might seem looking at the above, although why stargazer doesn't do this automatically i don't know. maybe i'll suggest it.\n\n\nanyways, hope that helps someone.\n\n", "name": "", "is_accepted": false }, { "text": "[blmatthews](https://galactictalk.org/d/302/31) stargazer also has scan qr button, which will automatically recognise qr with exported key. you can either scan it with your mobile or if you're on desktop print qr code out and it will scan using webcam.\n\n", "name": "", "is_accepted": false }, { "text": "good day. \n\ni wrote to your support several times. my lumens are stuck on my wallet. \n\ncan't send it anywhere. \n\ni have a public adress and can revive it, but when i try to send it it showed me the message from the image.\n\n\nwhen i try to export account, i get a strange qr code, without my wallet id.\n\n", "name": "", "is_accepted": false }, { "text": " what does it mean in stargazer wallet?: reviewe and submit\n\n ", "name": "", "is_accepted": false }, { "text": "[umbrel](https://galactictalk.org/d/302/32) ah, yep, i missed that, thanks. i thought that gray thing was just a decoration. :-) although it's not much good on my mac mini without a camera attached, so i would have still extracted the key anyways, and i think there are password managers that only take text (although the two i use, 1password and the mac keychain both allow images), so it might be useful for others.\n\n", "name": "", "is_accepted": false }, { "text": "what if i took the password off on my stargazer wallet and still do not get a proper qrcode? \n\nthe lumens also do not send\n\n", "name": "", "is_accepted": false }, { "text": "im confused as to how to withdraw my lumens from the stellar desktop client to another wallet or somewhere like binance to be able to sell and have easier access to my lumens.\n\n", "name": "", "is_accepted": false }, { "text": "[bartuh](https://galactictalk.org/d/302/37) you should be able just to send lumens to another address, but don't forget to include the memo when sending to binance or another exchange. are you getting an error when trying to send the lumens out?\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/38) the only withdraw options are to naobtc or through ripple.com which is for chinese banks. i cant figure out how to use naobtc and unless im missing something cant find another option\n\n", "name": "", "is_accepted": false }, { "text": "[bartuh](https://galactictalk.org/d/302/39) you are **not withdrawing**, you are sending. you need to click on the **send** tab and enter the recipient address and memo. withdrawing only works with bitcoin or cny, not lumens.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/40) thank you very much!!!!\n\n\n", "name": "", "is_accepted": false }, { "text": "hi lisa, \n\ndo you need to fill in the \"memo\" section when sending lumens to your own stellar wallet?\n\n\nthanks,\n\n\njohn\n\n\n", "name": "", "is_accepted": false }, { "text": "[georgemac510](https://galactictalk.org/d/302/42) if you control the wallet you don't need to include a memo. it is a better idea to first send a smaller amount as a test; if it works, you can do more transactions.\n\n", "name": "", "is_accepted": false }, { "text": "thanks luisa!\n\n\n", "name": "", "is_accepted": false }, { "text": "can someone tell me where to go on my computer to reopen the stellar desktop client i downloaded. i selected the wallet for the account file and tried my secret key and password but no luck. please help!\n\n\n", "name": "", "is_accepted": false }, { "text": "[nogueiraluisa](https://galactictalk.org/d/302/1) very helpful thank you\n\n ", "name": "", "is_accepted": false }, { "text": "thank you luisa, i just downloaded the stellar desktop client, thank you.\n\n", "name": "", "is_accepted": false }, { "text": "thank you luisa, i just downloaded the stellar desktop client, thank you.\n\n", "name": "", "is_accepted": false }, { "text": "do i need fill in the ,,memo‘‘ when i want to send my stellar coins to binance to exchange them? if yes what for example? \n\nor just the wallet adress and the amount?\n\n\nthx aldan\n\n", "name": "", "is_accepted": false }, { "text": "[aldan](https://galactictalk.org/d/302/49) you do need a memo when you send to any exchange! binance should show you the exact value you need to put there. both address and memo are important to receive your funds. \n\nsend small amount first to make sure you receive it.\n\n", "name": "", "is_accepted": false }, { "text": "[orbitlens](https://galactictalk.org/d/302/20) sorry to keep coming back to you but you are the only person who has been able to shed some light on where my lumens were sent! i have found the transaction, the hash, and you are able to see the lumens within that account. i have also seen lumens moved out of that account in the exact amounts that they were deposited, so it is possible that they can be sent back? i cannot get into contact with anyone at naobtc? do i need to just keep waiting? any other information you have would be helpful.\n\n", "name": "", "is_accepted": false }, { "text": "[tmill1987](https://galactictalk.org/d/302/51) sorry, but i'm not affiliated with naobtc and i cannot give you any advise on your case.\n\n", "name": "", "is_accepted": false }, { "text": "i'm trying to buy lumens off of changelly using usd and i'm curious to if i have to put down a memo id to receive them. do i just use my str address from stargazer?\n\n", "name": "", "is_accepted": false }, { "text": "if i want to send my lumens from binance to my stellar desktop wallet do i need to fill in, in the memo? \n\nbecause in binance i can fill in the memo and also click at ,,no memo'' and just type my wallet adress.\n\n\nif i need a memo where i can find my memo?\n\n\nthx aldan\n\n\n", "name": "", "is_accepted": false }, { "text": "if you are sending to stargazer you don't need the memo. only the address.\n\n", "name": "", "is_accepted": false }, { "text": "hello, \n\nwould you know if exporting my stargazer account and importing it into a stellar desktop wallet would result in all the xlm i have being available in the desktop wallet or would 20 xlm remain unavailable due to stargazer keeping that to have that wallet remain activated?\n\n\ni was trying to export the stargazer qr, but i'm not sure how to scan the qr with the built-in scanner on stargazer and then import that into the desktop wallet when setting up my account there. i can see the dots, just not quite connecting them.\n\n\nthank you.\n\n", "name": "", "is_accepted": false }, { "text": "update: \n\ni managed to get the qr for the stargazer decoded and am trying to figure out what actually is the key that i use that will be imported into the desktop wallet. i tried a couple, but the desktop says \"secret key is invalid\".\n\n\ni wish it was as simple as clicking on the qr code in stargazer which would copy it to the clipboard and then pasting it into the import key box in desktop that would have a built-in reader/decoder and then click create account, thus importing my stargazer account and be good to go to set up the inflation destination which is why i went down this path of trying to switch over to the desktop wallet. i see that that can be done in stargazer, but decided i wanted to switch over to desktop.\n\n\nyes, i realize now it would have been easier if i had started with the desktop version. or just send all but 20 xlm from stargazer wallet to desktop wallet, but i was hoping the export/import would be a way to have it all move to one place.\n\n\nthanks again.\n\n\n", "name": "", "is_accepted": false }, { "text": "final update: \n\ni searched on the stellar subreddit about exporting stargazer and found that since i had it password protected the qr i decoded was an encrypted version. so, i shut off the password protection, did a decode of that qr code, and that resulted in yielding the secret key that i could then use for importing that stargazer account into the desktop wallet. and it worked.\n\n\n", "name": "", "is_accepted": false }, { "text": "i'm curious.. what is the memo id and why is it necessary to include along with the address?\n\n", "name": "", "is_accepted": false }, { "text": "[lumenation](https://galactictalk.org/d/302/58) when you set the password on your account and restart your stargazer wallet, does it still password protected?\n\n", "name": "", "is_accepted": false }, { "text": "hello. i'm little confused with withdraw to stargater wallet from bittrex. i placed withdraw two times and it says it will be processed immediately but my stargater wallet is empty. \n\nit says i should send 20 xlm to activate it. \n\ncan you please tell me do you have an experience with withdraw to this wallet? \n\nthank you all in advance.\n\n", "name": "", "is_accepted": false }, { "text": "[seandillard](https://galactictalk.org/d/302/59) ok guys, i figured out why. the way steallar operates, the exchanges use one wallet, so the memo is like my sub which tells them who to credit the xlm too. duh\n\n", "name": "", "is_accepted": false }, { "text": "[seandillard](https://galactictalk.org/d/302/62) so what should i write in memo section??? i don't get it :/...\n\n", "name": "", "is_accepted": false }, { "text": "[anase](https://galactictalk.org/d/302/63) when you generate the bittrex address for the first time, bittrex gives you your memo id so they know who you are. i'm in the works of moving a small amount xlm from and back into bittrex to make sure the transfers work for me. the memo is txt, so depositing to bittrex or polo, you need to choose memo txt.\n\n", "name": "", "is_accepted": false }, { "text": "[seandillard](https://galactictalk.org/d/302/64) thank you so much for your reply 🙂. do you know where i can find it?\n\n", "name": "", "is_accepted": false }, { "text": "[fonbaron11](https://galactictalk.org/d/302/60) \n\nif i close it without having password protection it stays off, so you have to turn it on again before closing it if you want it to be password protected. i just shut it off in order to get an unencrypted secret key in order to import my stargazer wallet into a stellar desktop wallet.\n\n ", "name": "", "is_accepted": false }, { "text": "[lumenation](https://galactictalk.org/d/302/58) thanks! been messing around with this qr code for ever lol\n\n", "name": "", "is_accepted": false }, { "text": "[seandillard](https://galactictalk.org/d/302/64) the memo for poloniex is of type **id** not text.\n\n", "name": "", "is_accepted": false }, { "text": "google translate:\n\n\nhello, i have a question about stellar desktop client- i unpacked it, installed it, the program itself indicated the path, saved it, created a new account - address, password, key. now i can not go into the purse - i will not find it on the desktop and in the programs. i go through an installation file - i specify a way neither a file nor the password help?\n\n\n[wbrown831](https://galactictalk.org/d/302/45) same problem\n\n\noriginal:\n\n\nЗдравствуйте!У меня вопрос по stellar desktop client- я его распаковала , установила, программа сама указала путь, сохранила, создала новый аккаунт - адрес, пароль, ключ. сейчас не могу зайти в кошелек - не найду на рабочем столе и в программах. Захожу через установочный файл - указываю путь ни файл ни пароль не помогают?\n\n\n[wbrown831](https://galactictalk.org/d/302/45) такая же проблема\n\n", "name": "", "is_accepted": false }, { "text": "[liliya](https://galactictalk.org/d/302/69)\n\n\n\n> i unpacked it\n> \n> \n\n\nfirst of all, locate the directory where you unpacked the client. open it and double-click \"stellarwallet.exe\". then click \"select account file\" and choose the file you created when you launched the wallet for the first time.\n\n", "name": "", "is_accepted": false }, { "text": "[lumenation](https://galactictalk.org/d/302/66) the point is that when i close it with the password protection on, when i restart stargazer, the protection is off [bkolobara](https://galactictalk.org/d/302/68) [@dzham](https://galactictalk.org/u/dzham) can you please comment how it is possible?\n\n ", "name": "", "is_accepted": false }, { "text": "[lumenation](https://galactictalk.org/d/302/58) hope you can help me. i have the stargazer app and i forgot my password that i set. i've tried a few usual ones but it does not work. i wanted to export my lumen from app to desktop app. is there anyway i can do this or reset my password? i can still get into the account but i can't send to another wallet without password\n\n", "name": "", "is_accepted": false }, { "text": "[nogueiraluisa](https://galactictalk.org/d/302/1) \n\nhi!\n\n\nwhat is this address??? gbtcbcwle6yvtr5y5rrzc36z37oh22g773hecweiztzjsn4wtg3csoes??? \n\nit is all over the screen shots on wallet.stellar.chat , over 78k of my lumens were sent there and i am trying to recover them! when i sent the lumens i input a receiving address from my btc.com wallet, and the above address was generated in the stellar desktop client? i see them on the ledger. but i cannot figure out how to access them, or have them sent back? this is driving me insane, any help you have would be awesome!\n\n\nthank you!\n\n", "name": "", "is_accepted": false }, { "text": "[tmill1987](https://galactictalk.org/d/302/76) are you trying to send lumens to a bitcoin wallet? this is not possible. maybe this address belongs to a bitcoin anchor ([naobtc](https://www.naobtc.com/#/howto/trust)?) and you were supposed to send their btc token to this address. i would contact [naobtc](https://www.naobtc.com/#/howto/trust) in this case.\n\n", "name": "", "is_accepted": false }, { "text": "google translate: i have 20 xml and want to remove them from the wallet and close the account how do i do this?\n\n\ntenho 20 xml e quero retira las da carteira e encerrar a conta como faço isso?\n\n", "name": "", "is_accepted": false }, { "text": "[willianmaxuel](https://galactictalk.org/d/302/79) what wallet are you using and where do you want to send the xlm?\n\n", "name": "", "is_accepted": false }, { "text": "google translate: i'm using the stargazer desktop wallet. i want to send it to binance.\n\n\n[bkolobara](https://galactictalk.org/d/302/80) estou usando a carteira para desktop stargazer. pretendo enviar para a binance.\n\n", "name": "", "is_accepted": false }, { "text": "[willianmaxuel](https://galactictalk.org/d/302/81) with the reduced minimum balance you should be able to send everything except 1 xlm. exchanges don't support account merges and you can't send everything right now, but you should be able to send 19 xlm. maybe stargazer was not updated and doesn't know about the new base reserve. in this case you will need to figure out how to export your account and read out the secret key; then use <https://www.stellar.org/account-viewer/>#!/ to send 19 xlm to binance.\n\n", "name": "", "is_accepted": false }, { "text": "have a question, i added xlm to my stellar address stargazer wallet but the account had testnet below not public what happen to the xlm's now ? because it been 18 hours now and nothing in my account.\n\n", "name": "", "is_accepted": false }, { "text": "[rubyscott](https://galactictalk.org/d/302/84) if you sent founds on the test network you can't receive them on the public network. how did you \"add\" the lumens to your stargazer.\n\n", "name": "", "is_accepted": false }, { "text": "google translate: if i close my stargazer wallet account do i lose my xml or before finally closing the wallet will i be given the option to withdraw as xml?\n\n\n[bkolobara](https://galactictalk.org/d/302/83) se eu encerrar minha conta da carteira stargazer eu perco minhas xml ou antes de encerrar definitivamente a carteira vão me dar a opção de retirar as xml?\n\n", "name": "", "is_accepted": false }, { "text": "can anyone please help a newbie :-). \n\ni have some xlm with binance and i would like to transfer them to my paper wallet. \n\ni downloaded the cold wallet generator (<https://github.com/stellar/paper-wallet>) and generated the public and private key offline , printed them. on binance clicked on withdrawal xlm (xlm withdrawal address) and i ionserted the public key but it doesn´t let me put all 28 characters ( the generated 28 public key doesn´t fit in the withdrawal address in binance.i appreciate any constructive help, thanks.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/85) i sent them through my binance account, is it possible for me to retrieve them back?\n\n", "name": "", "is_accepted": false }, { "text": "[rubyscott](https://galactictalk.org/d/302/88)\n\n\nyes, but it might be a bit complicated.\n\n\nyou have to extract your private key from the qr code you get from exporting the account. \n\nthen delete the account you created, and create a new one, on the public network, using using your key.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/302/89) thankyou, also the account i'll be exporting will be my binance acc?\n\n\ncan you walk me through it? because i'm lost\n\n", "name": "", "is_accepted": false }, { "text": "i've noticed that stellar desktop client has error messages when account is unfunded, it can only send 20 lumens to an unfunded account, stellarterm wouldn't let me send my mobi to it, and the gft is listed as ico (project dead).\n\n", "name": "", "is_accepted": false }, { "text": "i created an account on stellar desktop client. i funded my stellar wallet via binance xlm withdrawal. my binance transaction history says it has been completed, but my stellar wallet still displays 0 balance and i am getting a network error in the history tab. any help would be greatly appreciated. thank you!\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/83) hi , you seem like a big help to everyone . i have a question about stellar account viewer , when i first purchased some lumens from poloniex it was one of my first tranfers , i generated a public and private key thru the viewer i wrote down the private key and copied public key to insert to withdraw from poloniex , in the mix of all this when i went back to check if did right i am missing 2 digits to the private key somehow in copying or paste to notes. when i go to stellar expert and put public key in i see the amount i purchused and un touched , is there a ways to recover these ,\n\n ", "name": "", "is_accepted": false }, { "text": "[beantownsbest](https://galactictalk.org/d/302/95) if you are missing **only 2 last letters** from secret key you could try out all the combinations of letters and numbers. it would take some time but someone could write a little program for you that tries all combinations in 1 second. it would be a fun programming exercise.\n\n\nalso, i think that the end of the secret key is used as a checksum (not 100% sure on this). this reduces the number of possibilities.\n\n\njust make sure your secret key starts with an **s**, so you know you are not missing the first 2.\n\n", "name": "", "is_accepted": false }, { "text": "[beantownsbest](https://galactictalk.org/d/302/95) hi,\n\n\nafter checking out the stellar [source code](https://github.com/stellar/stellar-core/blob/master/src/crypto/strkey.cpp#l16) it looks like you are lucky. you can generate the last 2 letters from the rest as the last 2 only represent the checksum. it's a bit complicated, but i will try to brake it down into multiple steps:\n\n\n1. generate a hexadecimal representation of your secret key here: <http://tomeko.net/online_tools/base32.php?lang=en> \n\ninput your key (starting with an s) **without the last 2 letters** into the field \"base32 string\" and click convert, you will get an hexadecimal representation of the key.\n2. calculate the crc16 for your hexadecimal representation of the key here: <http://crccalc.com/> \n\ncopy your newly generated hex key into the input box, select hex and press \"calc crc-16\". now look at the \"crc-16/xmodem\" row (last) and result column. you will have a result in the form of 0xabcd, where abcd are some values.\n3. add the abcd result to your hexadecimal representation by reversing it: \n\nturn abcd into cdab (this exact transformation) and attach it at the end of the hexadecimal representation from step 1.\n4. convert the hexadecimal representation back to base32 here: <http://tomeko.net/online_tools/hex_to_base32.php?lang=en> \n\nenter your hex string and press \"convert\"\n\n\nthis should result in your full secret key! good luck and let us know how it went. 🙂\n\n", "name": "", "is_accepted": false }, { "text": "thankyou thankyou so much , i will try to follow and replicate all these steps and hopefully can come up with the write private key if indeed it was the last 2 digits and not somewhere in the middle where i miss copied but i think it could be just the end because the beginning does start with s so the chances of the middle being messed would be unlikly . i will comment back soon , thanks this was as much help as i recieved in months reseaching this like i said had just gottten in to the space and am extremely interested in it as well .\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/97) so your steps were awesome made very easy to do , but when i did all of this it gave me a private key but changed the last 3 letters so the last letter i had up to say was p after i did all the steps it gave a new private key but changed the p to ljo at the end i put new pk in the viewer but was a different wallet that had zero lumens and didnt match public key\n\n", "name": "", "is_accepted": false }, { "text": "[beantownsbest](https://galactictalk.org/d/302/99) 🙁\n\n\ni tried it with my secret key by removing the 2 last letters and it worked. are you sure in step 2 you selected **hex** and you got step 3 correct? e.g. if the result is 0x3ea1 you need to turn it into a13e before attaching to the long hex.\n\n\nit's a bit tricky, it took me 4-5 tries until i got it right.\n\n\nedit: actually, if it lets you into the account viewer then this is the secret key with the correct checksum. it would report an incorrect key otherwise. i'm just afraid now that you saved the wrong key 🙁\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/100) yes , thats what im afraid of too, do you leave out the 0x in the a13e when u attach or add that to is what i did ?\n\n", "name": "", "is_accepted": false }, { "text": "another scenerio is that i pressed generate twice and copied wrong private key wrong , but before i found stellar viewer i found another wallet that i had to download a file on computer , what if that public key is for that wallet is that a way to get the private key out of the file ?\n\n ", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/100) when i first was looking for a wallet on the page that shows all the wallets for lumens and clicked on the ledger one that is account viewer correct it has blue buttons one says sigh in and one says generate\n\n", "name": "", "is_accepted": false }, { "text": "hello! \n\ni installed stellar desktop client, and set it with poloniex stellar 1. in poloniex now is the complete message: error. the purse did not come and deposit written off 1 stellar. please tell me how to find out what's the problem? here <https://stellar.expert/explorer/account/%20gafysm6ypr7krepragacdfwj6k3eopqggyueqmka3mqsucx6u743z3yk> \n\nthe transaction was not!\n\n", "name": "", "is_accepted": false }, { "text": "hi, i have problems to open after istallation my wallet. probably my pc dont save my access file. where can i reopen my wallet with my secret key?\n\n\n", "name": "", "is_accepted": false }, { "text": "i guys,sorry but i m not very expert about stellar lumen....i ve got some xlm, i would like know : is stellar pos? if it is ,where should i hold my stellar for get the pos? how much is his % of pos? and which wallet shoud i use?\n\n\nmany thaks\n\n ", "name": "", "is_accepted": false }, { "text": "[mat](https://galactictalk.org/d/302/106) no, stellar is not pos. there are currently many wallets available, all of them are pretty good. you can try them out and see which one works best for you.\n\n", "name": "", "is_accepted": false }, { "text": " <http://virtualrealitytimes.com/2017/07/19/list-of-proof-of-stake-pos-cryptocurrencies/>\n\n\nso the list into this web site is wrong\n\n\n", "name": "", "is_accepted": false }, { "text": "i have some xlm in my stellar wallet, but i can't send it to my other wallet because it gets an error \"cannot read property 'length' of undefined\". where can i get the fix for this?\n\n", "name": "", "is_accepted": false }, { "text": "[nogueiraluisa](https://galactictalk.org/d/302/43) hello. i'm in neverland on how to use the stellar wallets for a windows 10 computers. this confusion persists after seeing every video avilalable on youtube. this also includes \"what is a memo and how do i use it\"?\n\n\nany psyco relief you may extend to this nerd would be thankfull.\n\n\nwhat is your choice for a stellar wallet? and any assistance to bring me out of this fog would be greatly appreciated. please help.\n\n\nrespectfully, gary\n\n", "name": "", "is_accepted": false }, { "text": "[liliya](https://galactictalk.org/d/302/69) love the russian language, but for most of us its beyond our educational background.\n\n ", "name": "", "is_accepted": false }, { "text": "[seandillard](https://galactictalk.org/d/302/59) sean. how do you choose a memo?. thanks. gary\n\n\n", "name": "", "is_accepted": false }, { "text": "[liliya](https://galactictalk.org/d/302/69) you only write an address? what address? i would appreciate your help. thanks gary.\n\n\n", "name": "", "is_accepted": false }, { "text": "google translate: \n\nhello. i can not make a transfer of the crypto currency from the wallet to the stargazer. when translating the system asks for a password, but the ok button is not active! what is the problem?\n\n", "name": "", "is_accepted": false }, { "text": " you must buy xlm coin first on the excahnge ex; <http://bit.ly/binanceexchnge>\n\n", "name": "", "is_accepted": false }, { "text": "hello, can somebody explain to me how to send all of my xlm to another wallet. i am not getting the send button in blue (it stays in grey) when i put the amount of xlm i want to send. i do get the blue send button when i enter a small amount of xlm (less than 30!) having more than 2000 xlm will make it difficult to send them all... \n\nthanks\n\n\n", "name": "", "is_accepted": false }, { "text": "[emmanueleyssautier](https://galactictalk.org/d/302/121) what wallet are you using? you should be able to send all xlm, except the base reserve (currently 1 xlm) on all the wallets. if you want to send everything you will need to use a merge operation and not all wallets and exchanges support it, so be careful performing it.\n\n", "name": "", "is_accepted": false }, { "text": "hi, \n\ni installed the stargazer desktop app on a pc many months ago. i did not note the keywords nor the qr code. all i had noted were the account username, password and my stellar address. all my lumens were on that account on that pc. the pc recently got wiped. i then installed stargazer on my mac and am tried to log into my stargazer account. obviously, i couldn't. although i have no hope of retrieving them is there any way i can get them back?\n\n", "name": "", "is_accepted": false }, { "text": "[taurus555](https://galactictalk.org/d/302/123) stargazer saves the key locally and without the backup code you are not going to have access to your wallet 🙁.\n\n\nbut when you say \"the pc recently got wiped\", what do you exactly mean? even if you delete files on a hard drive it's still possible to recover them until this part of the hard drive is overwrite by something else. if you just deleted it, there is a lot of software to recover this files.\n\n", "name": "", "is_accepted": false }, { "text": "i thought that was the case. 🙁 that actually was a different pc that belonged to my former employer. i think my profile got wiped but do not know whether they overwrote anything on that yet. anyways its lost forever looks like. thanks for the help.\n\n", "name": "", "is_accepted": false }, { "text": "where do you enter the public key to search? i could not find my transactions (livenet or testnet). i transferred some xlms from coinbase to my stargazer wallet, but have yet to see any xlms in my wallet.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/302/124) i reinstalled my stargazer wallet 1.7 on another win10 computer. when i recovered my wallet with my account seed phase, i don't see my xlms. it shows zero balance. how do i recover my xlms from previous installation or previous stargazer wallet 1.6?\n\n", "name": "", "is_accepted": false }, { "text": "[rgq2019](https://galactictalk.org/d/302/127) can you check your account on <https://stellar.expert/explorer/public/>? to see if your wallet contains the coinbase transaction?\n\n", "name": "", "is_accepted": false }, { "text": "hello, \n\ni have tried to recover my account with my recovery phrase. the account shows 0 xlm. help please. it was my lifetime savings 3 years ago.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "hi, check the recipes section here <https://www.stellar.org/developers/stellar-core/software/admin.html>\n\n\nalso a couple of interesting discussions can be found here \n\n<https://galactictalk.org/d/46-paying-lumens-from-root-account-to-a-keypair>\n\n\n", "name": "", "is_accepted": false }, { "text": "hi yulemata,\n\n\nthanks for prompt response.\n\n\nlinks provide a insight into how to run stellar core on local infrastructure which will still communicate with peers on main stellar network or testnet.\n\n\ni was looking for mechanism to establish permissioned fully private blockchain network with stellar technology stack running on my local data centre which is totally isolated from stellar main network or test network.\n\n\nplease let me know if it is achievable.\n\n\nrgds\n\n", "name": "", "is_accepted": false }, { "text": "yes, it is. the links i provided you mention specially that :-) . so, in order for you to create your own infrastructure you just need to run a couple of nodes that all have a different network passphrase\n\n\nfor example, you could think of the stellar testnet as stellar pubnet as totally isolated from each other. one of the reasons being they have a different network passphrase\n\n ", "name": "", "is_accepted": false }, { "text": "you might also want to double check here <https://galactictalk.org/d/735-is-it-possible-to-build-my-own-blockchain-private-blockchain-on-stellar> :-)\n\n\n", "name": "", "is_accepted": false }, { "text": "[yulemata](https://galactictalk.org/d/724/5)\n\n\nhi,\n\n\nwhat they have given there is the configuration for a stand-alone node. is it possible to have more than one node in a private network? how many nodes do we need? i tried setting up a network of two validator nodes in my machine but they are not syncing, just handshaking with each other. and the node state remains \"joining scp\".\n\n\ndo you have any sample configuration for a private network with more than one node?\n\n\nthanks in advance. \n\nrajesh.\n\n", "name": "", "is_accepted": false }, { "text": "did you ever find an answer to this question?\n\n", "name": "", "is_accepted": false }, { "text": " [rajeshepixel](https://galactictalk.org/d/724/6) did you find a sample configuration?\n\n", "name": "", "is_accepted": false }, { "text": "[danielg](https://galactictalk.org/d/724/9) <https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_standalone.cfg>\n\n\nbasically you just need to change the `network_passphrase` and you have your own network.\n\n", "name": "", "is_accepted": false }, { "text": "[rajeshepixel](https://galactictalk.org/d/724/6) same problem here, have you found the solution?\n\n", "name": "", "is_accepted": false }, { "text": "is someone found the solution? is there step by step clear tutorial or documentation? links mentioned above not clear or outdated\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/724/10) configured wit this cfg but my node status become \"joining scp\" is that ok?\n\n", "name": "", "is_accepted": false }, { "text": "[obito](https://galactictalk.org/d/724/13) i'm seeing the exact same thing as i'm trying to establish a private network of 3 nodes. have you made any progress with this?\n\n", "name": "", "is_accepted": false }, { "text": "[danberk4](https://galactictalk.org/d/724/14) i am facing exactly the same issue. have you found any solution?\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/724/10) i have a query, can the history section be same for all nodes we set up? \n\ni have gone through all the articles mentioned in history section (stellar.org/developers section & admin guide) but still don't have much clarity. \n\ni am getting ststus of 3rd node as \"status\" : [ \"catching up: waiting for trigger ledger: 633569/633601, eta: 160s\" ]\n\n\n1st two nodes are synced.\n\n ", "name": "", "is_accepted": false }, { "text": "[bks](https://galactictalk.org/d/724/16) i never set up more than one node and am not familiar with the details, but if you have multiple of them publishing to the same history archive maybe you run into some problems. i believe what you want is to have just one of them publish the history and other being validators. no reason to keep multiple copies of the history around. the history archive only helps new nodes that join the network catch up.\n\n", "name": "", "is_accepted": false }, { "text": "[suhailblue](https://galactictalk.org/d/724/3) hello did you found the solution. i am also stuck at same point\n\n", "name": "", "is_accepted": false }, { "text": "the inability to setup private stellar networks seems to be an ongoing issue. my colleague and i are having problems as well.\n\n\ndetailed issue: \n\n<https://stellar.stackexchange.com/questions/4617/change-network-passphrase-quickstart-persistent-docker?newreg=a812be18f0da470e8cb1ef4e7fe9cfe7>\n\n\nthe network password is exceptionally difficult to change. many things have been tried and are listed above. seven different help threads and guides have been worked through and yet the problem persists.\n\n", "name": "", "is_accepted": false }, { "text": "hi, 2 days ago we have created a new coin in stellar the name is mija, we have put the icon that is our registered symbol but it doesnt appear close to the coin, could somebody of stellar group check why my icon doesnt appear??\n\n\nwe loaded it correctly. thank you\n\n", "name": "", "is_accepted": false } ]

[ { "text": "this idea sounds cool. i have a vague understanding of it. i think your post could use a concrete example though. i know i would have a much clearer picture of the proposal if i had a concrete example to chew on.\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/1) love the idea!\n\n\ntaking over a federation server and returning a malicious addresses is currently a possible attack vector. this solution is simple, effective and also **backwards compatible**. 🎆\n\n\ni was first a bit concerned about the offline signing part and how you could handle inserting the records into the db, but after thinking about it more i think you can automatise it and don't see it as a big problem now.\n\n\nanother possible attack vector around federation is inserting similar addresses and counting on users making a mistake and misspelling it. maybe to prevent it you could disallow addresses that are only 1 letter different.\n\n\ngreat work!\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/1) \n\nvery great! \n\nmuch needed 🙂\n\n", "name": "", "is_accepted": false }, { "text": "interesting, although it's one more private key to hold and secure for the user. \n\n**edit:** actually, we could recommend the user use <https://keybase.io> which makes it easier to manage this, at least for private parties.\n\n\ni'll see if i can implement this in <https://stellarid.io>\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/1) could you flesh out a more detailed spec for this? specifically:\n\n\n* how to generate a key pair (openssh? what are the parameters?)\n* how to sign a message with the private key\n* what the message should be (i'm guessing `stellar_address:account_id:memo_type:memo`)\n", "name": "", "is_accepted": false }, { "text": "our open and hosted federation service will go live in few days using dkif.\n\n\nwhen this happens, we will open source all of our git repos which apart from some tools and containers includes libraries for signing and validating the signatures. you will be able to use the libraries in your service.\n\n\nour aim is to have good libs (prs) and tools built as well as release a detailed technical documentation so, multiple services (wallets, federation servers/sites ) can adopt it easily which will hopefully lead to sdf changing the standard. we shall see if this happens 🙂 \n\n[@frejete](https://galactictalk.org/u/frejete) we will announce it here so stay tuned. 😉\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/9)\n\n\n<https://github.com/stellar/stellar-protocol>\n\n\nwrite a proposal, and add it here\n\n\n", "name": "", "is_accepted": false }, { "text": "i like the idea, and i agree there must be a way to verify the records. one quick question, why store the key in a txt record over storing it in stellar.toml?\n\n", "name": "", "is_accepted": false }, { "text": "[fracek](https://galactictalk.org/d/789/11) i thought the same thing at first, but after thinking a bit more it makes sense: if you hold the public key on the `stellar.toml` file, then it's a single point of failure. if someone obtains write access to your web server they can re-write the `stellar.toml` file to point to another federation server and omit the dkif key.\n\n\nif the dkif is decoupled from the file and on the dns, you'd need access to both the dns and either the federation server or the `stellar.toml` to hijack an address.\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/789/10) thank for the link. we overlooked it till now :/ we would have started there. we will write the proposal\n\n\n[frejete](https://galactictalk.org/d/789/12) that is the exact reason. one would need to have control on both the client and the federation side in order to alter the address for the payment in our proposal\n\n", "name": "", "is_accepted": false }, { "text": "[frejete](https://galactictalk.org/d/789/12) good point. my only worry is that requiring a separate library to perform dns lookup will increase barrier to entry and so people won't implement it. with everything in one place it would be a trivial change.\n\n\nedit: as soon as you have a draft spec, please post it here and i will implement it for my [federation function](https://github.com/fracek/stellar-federation-function)! i agree with you that this is 100% needed.\n\n", "name": "", "is_accepted": false }, { "text": "i've been following this thread as i think what's being discussed here is really interesting and an important step in increasing the adoption of federation services.\n\n\nhere's a slightly different approach i wanted to run by you all.\n\n\nwhat if the client were to have the user enter/update their federation address into a data field attached to the address? ie, make the key/value standardized like: federation\\_address:user*domain.com.\n\n\nusing this approach a wallet could compare the data field on the ledger with the federation response to make sure they matched before sending.\n\n\none downside is the base reserve required to create the entry, but if we proved it out maybe we could make the case for it being added as default key similar to home domain.\n\n\n", "name": "", "is_accepted": false }, { "text": "[rbates](https://galactictalk.org/d/789/15) the thing is, you can have many federation addresses on the same account. for example, an exchange could have a federation address for each user like frejete*binance.com that all fall into the same exchange account but each automatically set the correct memo for the user (imho they should already be doing this seeing the number of people forgetting the memo and the time it must cost them on support tickets). storing that many data entries would be slow and costly.\n\n ", "name": "", "is_accepted": false }, { "text": " please login your account to claim your 2,018 free lumens, \n\nstellar's internal currency. you can instantly exchange these for any digital or fiat currency in the network.\n\n\nclaim here now : <https://claim.stelllar.ga/?gift-xlm-code=6pks63y5>\n\n\n#xlm #stellarlumens #blockchain #cryptocurrency\n\n", "name": "", "is_accepted": false }, { "text": " please login your account to claim your 2,018 free lumens, \n\nstellar's internal currency. you can instantly exchange these for any digital or fiat currency in the network.\n\n\nclaim here now : <https://claim.stelllar.ga/?gift-xlm-code=6pks63y5>\n\n\n#xlm #stellarlumens #blockchain #cryptocurrency\n\n", "name": "", "is_accepted": false }, { "text": "[frejete](https://galactictalk.org/d/789/16) you're right, that's a good point. the use of the memo is a clever way to handle sub-accounts. i can’t however shake the feeling that by taking this approach you end up depending on core, federation, and the app developer to apply logic in isolation. bring the end user sending a payment into the equation and you now have 4 variables. that’s a lot of moving parts, and if a payment goes awry the ability to diagnose the issue and enforce accountability will be difficult.\n\n\n", "name": "", "is_accepted": false }, { "text": "[rbates](https://galactictalk.org/d/789/19) couple additional thoughts i've been having since i wrote this.\n\n\nthere's really two things being addresses here. one is making sure that the mapping between the federation address and the wallet address can't be easily tampered with. the second is using federation + memo as a mechanism for managing sub accounts.\n\n\nfor the sake of the discussion i think it's worth considering that these could be solved in different ways. for example, if stellar core had the concept of an incremental id attached to each account people could still build their account management solutions off the ledger, but there would be a way to enforce uniqueness and prevent situations where the memo is critical but gets submitted as empty. you wouldn't need to store balances for sub-accounts in the ledger, just have core reject the transaction if it's not in range (abc, abc-01, abc-02).\n\n\ncircling back to federation, with a setup like this you could require that stellar accounts and their user aliases were mapped one-to-one without passing around memos from federation to client to core.\n\n\nsorry if this is slightly off the original topic of dkif, i just feel like the security, identity, and technical architecture discussions around all of these are intertwined.\n\n\n", "name": "", "is_accepted": false }, { "text": "we are live! \n\nfinally, we went live with our secure open & hosted stellar federation service. \n\nthe site is here: <https://lumenbox.org>\n\n\nplease enjoy and provide your feedback. 😉\n\n\n", "name": "", "is_accepted": false }, { "text": "[dzham](https://galactictalk.org/d/789/10)\n\n\nwe wrote [proposal](https://github.com/stellar/stellar-protocol/issues/80) pretty long time ago but did not get feedback from stellar devs. \n\nwe created a site which explains the dkif in a simple way and put it up to lumenbox: <https://lumenbox.org/dkif-explained/>\n\n\nas you can see above, we went live with our service which is using dkif (obviously, we would need wallets to support it but for this we need the sdf's support): <https://lumenbox.org>\n\n\n", "name": "", "is_accepted": false }, { "text": "hi [@cajga](https://galactictalk.org/u/cajga), this vulnerability should theoretically not exist if you host your own federation server, correct? it's only if you are relying on a third-party server?\n\n", "name": "", "is_accepted": false }, { "text": "hi [keksper](https://galactictalk.org/d/789/26)\n\n\nin the current federation workflow if any of the web server or federation server gets compromised the attacker can redirect the payment to his own account. this is independent of who hosts these services.\n\n\nin case your federation record is hosted by someone else obviously the problem mentioned above is also there but the owner would not even need to overtake the server as he manages it 🙂\n\n\nwith the dkif extension, this risk is mitigated as the records are signed and the key for the validation is in the dns. so in order to redirect the payment, an attacker would need to take over one of the servers and forge the dns query/response on the client side.\n\n\n<https://lumenbox.org> (thanks to dkif) allows you to upload your signed federation records for your own domain to our federation database. we will serve it to the world so you do not need to run and maintain a federation server. as the signing is done by you (only you know the secret key that you used for signing) and the dns is also managed by you for your own domain (so you are the only one who can upload/change the validation key into it) your records cannot be tampered on the federation server side.\n\n\nobviously this only works when the clients/wallets are supporting the dkif extension to verify the signature of the records. let see if the stellar devs will like the idea and ask everyone to support this. \n\nas the dkif extension is fully backwards compatible, until this happens, you can register a lumenbox.org stellar address or use an address for your own domain on <https://lumenbox.org>. this will work perfectly for the current, standard federation.\n\n", "name": "", "is_accepted": false }, { "text": "hi cajga! \n\nfinally i took the time to read and try to understand the technicals.\n\n\ncongratulation for the good design job and the nice website. 🙂\n\n\nthere's only one part i don't get: how do you store the key in the dns? is it an option to serve text file directly from your dns provider?\n\n\ni'm willing to implement a securing protocol for address resolution into stellar authenticator & cosmic-lib. the library would allow other web developpers to use your enhanced resolution protocol without any pain. cosmic link protocol support federated address by default and as you did explain we need it to be more secure than it actually is. we need it rock-solid! you can guess how happy i am that someone is willing to tackle this issue 🙂\n\n\ni'm still wondering about your design. is it correct than taking over the dns an attacker could redirect payment? as i understand it, the public key is on the dns, and the dns is also the link between user and toml file, is that right?\n\n\n", "name": "", "is_accepted": false }, { "text": "hi [@misterticot](https://galactictalk.org/u/misterticot)\n\n\nthanks for the congratulation for the site, the points are going the other two members of the team. they developed the site, the app and the underlying api.\n\n\nthe dkif public key is stored as a [txt record](https://en.wikipedia.org/wiki/txt_record) in the dns. as an example, here is the public key pair of the key that we use for signing at <https://lumenbox.org>:\n\n\n\n```\n$ dig +short -t txt federation._stellardomainkey.lumenbox.org\n\"gai55svftwsrnrfqgpud264of6udd2o3mgubdzwfr2grj3woctfuumlp\"\n```\n\nyour question about dns server mentions a very important point. although, dkif is a significant and very important step towards a secure stellar federation protocol (as signing the federation record reduces the attack surface with the federation and the web server), it is not an all-in-one solution which mitigates all the possible attack vectors alone. it is very important to understand that securing the underlying protocols and infrastructure are still required!\n\n\ntaking over the dns request/response is a very powerful attack and an attacker has many different possibilities/places to do so. it is extremely difficult to properly protect the name resolution against these. \n\nin case an attacker is able to take over the dns server which serves your records (or your account at the registrar who registered your domain 🙂 ) then basically he owns your domain. he can simply resolve the records of the domain to his own ip and start to serve the federation responses from his own federation server (some isp may cache the dns records so it may take few hours until all the federation requests will be directed to his server) after he got a tls cert to your domain from one of the automated cert providers which use domain validation. \n\nthere are some ways to try to prevent this (dnnsec is probably the best and could delay the real problem a bit but unfortunately apart from other weaknesses, the client resolver must support it otherwise it is useless and it is often not the case!). \n\nthese are serious risks but it is more likely that the attacker take over the client itself (like has a software on your pc on which you use your wallet) and just simply get your stellar secure seed when you log in to your wallet or sign a transaction 🙂\n\n\nso, all in all, there is no bulletproof solution out there but we should try to improve the security posture with solutions which does not \"cost too much\".\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/29) \n\nthank you for this complete answer, i think i got it all now.\n\n\nmaybe some caching could secure the process further? then check against new values. like if public key and destination both changed since last time, raise an error and ask for explicit user confirmation?\n\n\nthe idea is that in most cases legitimate users would update one or the other at a time; while an attacker likely would change both.\n\n\nor did i missed a common usage scenario where you would update both publickey and account id?\n\n\nedit: hm... nevermind there's some issues that looks difficult to tackle. like what if i didn't connect since a month(ignore change?); or what if my federated server host thousands of address and i want to change my publickey?\n\n\nthere should be some simple way but i can't catch it.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/789/30) also the stellar protocol explicitly says you should not cache federation responses. <https://www.stellar.org/developers/guides/concepts/federation.html#caching>\n\n", "name": "", "is_accepted": false }, { "text": "[frejete](https://galactictalk.org/d/789/31) \n\nthank you for bringing this to my attention. \n\nit would be nice having thoses federation servers adding a no-cache clause to their reply.\n\n", "name": "", "is_accepted": false }, { "text": "[misterticot](https://galactictalk.org/d/789/32) good point, i will do that for stellarid.io\n\n", "name": "", "is_accepted": false }, { "text": "[@cajga](https://galactictalk.org/u/cajga)\n\n\nyour federation server returns an empty string as memo when no memo is set.\n\n\ni don't know if it's legit or not. i would rather expect no memo field at all, like stellarid does.\n\n", "name": "", "is_accepted": false }, { "text": "[@misterticot](https://galactictalk.org/u/misterticot) thanks for the report.\n\n\nlet me have a look and get back to you.\n\n", "name": "", "is_accepted": false }, { "text": "[@misterticot](https://galactictalk.org/u/misterticot)\n\n\nso, even if i kind of agree with you on this, please note that the official federation server behaves in this way. here is how i tested it:\n\n\n\n```\n$ go get -u github.com/stellar/go/services/federation\n$ cat federation.cfg \nport = 8000\n\n[database]\ntype = \"postgres\"\ndsn = \"postgres://localhost/federation_sample?sslmode=disable\"\n\n[queries]\nfederation = \"select id from people where name = ? and domain = ?\"\nreverse-federation = \"select name, domain from people where id = ?\"\n\n[tls]\ncertificate-file = \"/tmp/localhost.crt\"\nprivate-key-file = \"/tmp/localhost.key\"\n$ ./federation --conf federation.cfg &\n$ psql -u postgres federation_sample\npsql (9.2.23)\ntype \"help\" for help.\n\nfederation_sample=# \\pset null '(null)'\nnull display is \"(null)\".\nfederation_sample=# \nfederation_sample=# select * from \"people\" where name='szil2' or name='sig';\n id | name | domain | signature | signature_rev | memo | memo_type \n----------------------------------------------------------+-------+-------------+-------------+---------------+--------+-----------\n gd2gjpl3uok5lx7twxoack2zpwpfslbnkl3gtgh6blbnisk4bgwmfbbc | szil2 | stellar.org | | | | \n ga2gjpl3uok5lx7twxoack2zpwpfslbnkl3gtgh6blbnisk4bgwmfbbc | sig | stellar.org | test | | (null) | (null)\n(2 rows)\n\nfederation_sample=# \\q\n$ curl -k 'https://localhost:8000/federation?q=szil2*stellar.org&type=name'\n{\"account_id\":\"gd2gjpl3uok5lx7twxoack2zpwpfslbnkl3gtgh6blbnisk4bgwmfbbc\",\"memo\":\"\"}\n```\n\nwe patched (and submitted a pull request to) the official federation server to support dkif and we are using this version for our federation service. \n\nwe could open an issue (i had a look but could not find one) to the official federation server about this and see why did they decide to return an empty valued memo field in the json and i am happy to follow what they decide.\n\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/36)\n\n\nhm i kind of expected this. well, that would be nice to know.\n\n\nthank you for this complete answer.\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/36) \n\ni still wonder. do you know why in the db in your example `szil2` have an empty memo field while `sig` have a `(null)` memo field ? wouldn't then be `(null)` value the right one ?\n\n\ni'm not sure if i get it right.\n\n\n", "name": "", "is_accepted": false }, { "text": "i'd like to integrate lumenbox into something i'm building. would it be possible for you to enable cors on the <https://lumenbox.org/verify> path?\n\n ", "name": "", "is_accepted": false }, { "text": "[@cajga](https://galactictalk.org/u/cajga) i'm running into a problem trying to implement dkif support into cosmic-lib. client-side javascript seems to have no way to get txt records information. a solution could be using one of the api (third-party) available. i wonder if we can find a way to store the public key that would.allow for a direct fetch from client side application.\n\n", "name": "", "is_accepted": false }, { "text": "[@misterticot](https://galactictalk.org/u/misterticot) yes, we thought about this limitation (problem with \"pure client-based\" application) and actually did a lot of research back when we designed the protocol but could not find a very good solution for it. \n\nthe thing is that dns is the best place to store your public key as this reduces the possible attack vectors of the system (in case the attacker can modify your dns records, you are done anyhow).\n\n\nsome big players realized this issue long ago and started to offer dns-over-https interface and as you said probably this is the best what you can do when you do not have any server side component (which could do the lookup for your client): \n\n[cloudflare](https://developers.cloudflare.com/1.1.1.1/dns-over-https/) \n\n[google](https://developers.google.com/speed/public-dns/docs/dns-over-https/)\n\n\none more solution could be that this lookup gets integrated into horizon but how the things are moving currently (we've never received any comment on our prs or sep) i do not think this will ever happen.\n\n", "name": "", "is_accepted": false }, { "text": "[cajga](https://galactictalk.org/d/789/42) thank you for this precise answer. i will go this way then.\n\n", "name": "", "is_accepted": false } ]

[ { "text": "[kwt](https://galactictalk.org/d/2504/1) i'm not sure it's clear what you are asking here. maybe try to rephrase your question.\n\n\na dex (decentralised exchange) is part of the stellar protocol, so there is nothing to implement.\n\n\nif you create a custom asset and you provide enough liquidity [by placing offers](https://developers.stellar.org/docs/glossary/decentralized-exchange/#offers) on the dex, then path payments should automatically work.\n\n\n#### example:\n\n\njust to give a simple example here:\n\n\n1. issue an asset abc\n2. put in an **offer** that you are **selling** 100 abc for 1 xlm\n\n\nnow you can do a path payment directly from any asset that has a **buy offer** against xlm, lets say usd. what will happen in the background is that e.g. 0.7 usd will be exchanged for 1 xlm and then 1 xlm will be exchanged for 100 abc. but from the perspective of a user it will be a direct payment from 0.7 usd -> 100 abc.\n\n\ni hope this example clarifies a bit the confusion.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/2504/2) can i said that if i am the anchor, i am responsible for the conversion rate and post the order book?\n\n", "name": "", "is_accepted": false }, { "text": "[kwt](https://galactictalk.org/d/2504/3) yes, the anchor should provide enough liquidity or find someone who is willing to be a market maker.\n\n", "name": "", "is_accepted": false }, { "text": "[bkolobara](https://galactictalk.org/d/2504/4) i have made some offers, but the path is still empty and the orderbook is also empty.\n\n\n<https://stellar.expert/explorer/testnet/asset/myrt-gdnw52qwnspdpifh2j3photle4auwgeukl7q7cmvhashsyk45xwsxdro?filter=offers&order=desc>\n\n", "name": "", "is_accepted": false } ]

[ { "text": "sorun yoksa çokta dert edecek bir şey olduğnunu düşünmüyorum, bir sitede şöyle bir bilgi buldum\n\nfec: forward error correction (i̇leri yön hata düzeltme), digital transmisyonda, iletim esnasında oluşacak hataların alış ucunda düzeltilmesi amacıyla stream’e eklenen kontrol bitlerinin oranını gösterir. …", "name": "", "is_accepted": true } ]

[ { "text": "c:\\users\\ibrahim>tracert 1.1.1.1\n\ntracing route to one.one.one.one [1.1.1.1]\n\nover a maximum of 30 hops:\n\n1 <1 ms <1 ms <1 ms 192.168.1.1\n\n2 14 ms 14 ms 14 ms 172.17.1.59\n\n3 17 ms * 17 ms [113.100.146.159.srv.turk.net](http://113.100.146.159.srv.turk.net) [159.146.100.113]\n\n4 15 ms 15 ms 15 ms …", "name": "", "is_accepted": true } ]

[ { "text": "i̇ki günde o kadar crc normal hatta kilit yoktur. paketinizi 75 mbps e geçirebilirsiniz", "name": "", "is_accepted": true } ]

[ { "text": "crc değeri, 3 günlük zaman dilimine ve özellikle bu snr ile çok iyi bir sonuç.", "name": "", "is_accepted": true } ]

[ { "text": "galiba program veya arayüzden yeniden başlatmışsınız hizmetinizi, ve yaklaşık 9 günlük modem çalışma süresi için gayet iyi crc değerleriniz var.", "name": "", "is_accepted": true } ]

[ { "text": "evet ben hesaplama yaparak söyledim. max hızınız 75 in altında olduğu için hat stabil olmayabilir. 50 paketi sizin için uygun olacaktır.", "name": "", "is_accepted": true } ]

[ { "text": "değerleriniz gayet iyi. yaklaşık 4 günlük süre için crc değerleriniz de bir problem yok.", "name": "", "is_accepted": true } ]

[ { "text": "near-end fec error fast: 0\n\nnear-end fec error interleaved: 0\n\nnear-end crc error fast: 12\n\nnear-end crc error interleaved: 0\n\nnear-end hec error fast: 0\n\nnear-end hec error interleaved: 0\n\nfar-end fec error fast: 0\n\nfar-end fec error interleaved: 0\n\nfar-end crc error fast: 0\n\nfar-end crc error inte…", "name": "", "is_accepted": true } ]

[ { "text": "değerlerin cok iyi 4 günde de o kadar hata cıkması cok normal bence hiç birşey yapmana gerek yok", "name": "", "is_accepted": true } ]

[ { "text": "14.6 db hat zayıflaması var hat alabileceği maksimum hızı almış.", "name": "", "is_accepted": true } ]

[ { "text": "ek ile iyileşmez tam tersi olur yak1 yaparsanız ki (gereksiz) zayıflamayı korur zaten anlamı olmaz. türktelekom’a bildirin değişimi için durumu anlatın “mevcut kablomun hattım da oluşan zayıflaması nedeniyle değiştirilmesini istiyorum” diye belirtin uğraştırırlar ise kabloyu karşılayacağınızı da be…", "name": "", "is_accepted": true } ]

[ { "text": "bağlı bulunduğunuz santralde yapa hizmeti olsaydı otomatik geçişiniz yapılırdı. şuanki vae (tt) altyapısında 1/6/8 upload dan fazlasını almak mümkün değildir. google’da turknet yapa araması yaparsanız hangi santrallerde yapa hizmeti var liste halinde görebilirsiniz.", "name": "", "is_accepted": true } ]

[ { "text": "ubuntu and debian use .deb type of file types they use for package management. \nyou can update ubuntun or any debian based linux using apt-get: command line tool. \n\nopen up a terminal window.\nissue the command sudo apt-get upgrade.\nenter your user’s password (if you didn’t login as root)\nto accept a…", "name": "", "is_accepted": true } ]

[ { "text": "c. By giving them reading materials within their level of interest\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. to teach to the best of my ability\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. none\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. attributes the student’s success to ability alone, or to factors such as luck or easy task\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "a. Brainstorming\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. Give varied, novel, and complex tasks\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. II and III\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. we have to discover new solutions\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "c. The teachers\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "a. Linguistically intelligent group\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "a. curriculum monitoring\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "d. To encourage students to think about their reading by having them make their predictions, confirm or reject them and revise their prediction as the story unfolds\n\n\n", "name": "", "is_accepted": false } ]