Hello everyone! I am a full stack software developer at Stockholm, Sweden. In case you want to know more or get in touch, here is my github https://github.com/yilmazuur and linkedin https://www.linkedin.com/in/yilmazugur . About the project, any feedback or comment would be very much appreciated. Since the project is in an early stage, any opinion would be even better. So, here I go: The idea is pretty straightforward in my opinion. However, doing it in a good way is a bit challenge that we are in. CelestialPay is about buying stuff with lumens. Any stuff you can imagine like iphone, laptops, subscription fees, pens, books etc. Using lumens as a fiat. If there is a seller ofcourse. So, this system should correspond both the seller and the buyer. On the buyer side, it is a special wallet that user can spend and keep track of his/her money(yes it is a money, celestial money). User can also use this wallet as a regular wallet app in the mobile phone. On the seller side, it is an API Service Provider which corresponds to wallet holders. E-commerce web sites, second hand sellers or anyone you can imagine who wants to receive online payments. There is one more usage. Bloggers or donation collectors will be able to receive lumens by celestialpay.me from celestial wallet holders. This time it is celestialpay.me not the api because this one is much easier and the person who sends lumens doesn't expect anything in return. To sum up: It is a wallet... No, an api... Oh, it is a website... Noo, it is CelestialPay. I am really deeply sorry to quote from Superman. But I couldn't hold myself back ? Basically, what we are trying to do is creating an environment for celestial wallet holders, an environment that you can buy, sell stuff or spend lumens as money or send/receive lumens as usual. My favourite part of this project is how we are going to do it. All the data will rely on horizon. Apart from that celestial environment will only be transaction initiater. So, our aim is not to hold or show any long or unsecure keys around. Secret keys will only be hold in the phone of celestial wallet holders and will be encrypted. I will come back later with more informations, screenshots and links. All the best ------------------------------Update------------------------------ Basic use case is payee initiates payment request from the ways described above and payer sends lumens using celestial wallet. It works only this way, because users' secret keys are only stored in users' phones (encrypted). All of the celestial services are free, no hidden percentage on anywhere. Here are the prod links: https://celestialpay.com - celestial website and download place of celestial wallet http://service.celestialpay.com/docs/v1/index - api documentation to request payments http://celestialpay.me/?uguryilmaz21@gmail.com - donation or crowdfund website which is automatically created for every wallet users, they can use it like this http://celestialpay.me/?registered_email_to_celestial_wallet I wrote mine as example. Here are the public issue trackers: (feel free to enter or vote ticket) https://bitbucket.org/yilmazuur/celestialwallet/issues https://bitbucket.org/yilmazuur/celestialpayapi/issues https://bitbucket.org/yilmazuur/celestialpay-website/issues https://bitbucket.org/yilmazuur/celestialpay.me/issues Feel free to give any feedback. Best

Have you looked into improving an existing wallet rather than starting a new one from scratch? You're still eligible for the SBC by doing so.

dlohnes Hi, thx for the comment. It came to my mind as well. There is this saying I like "If you want to go fast go alone, if you want to go further go with a team." So, as an answer I am totally open for collaboration, but I don't want to spend time for seeking that collaboration at the moment.

CelestialPay - Wallet, payment api and so on

yilmazuur

Hello everyone,

Waiting for app store approval of celestial wallet and working on celestial api website. Hopefully it will be done in couple of days as well.

In the meantime, I have created couple of issue trackers and added some actual(not sample) tasks regarding celestial products.
Please feel free to add tasks, report bugs, vote or comment existing ones etc.
Unless it is super critical, these tasks will be ongoing work after celestial mvp releases, which means issue trackers will be used after this build challenge and it will help to next build challenge as improvement of celestial stuff.

Here are the public issue trackers:
https://bitbucket.org/yilmazuur/celestialwallet/issues
https://bitbucket.org/yilmazuur/celestialpayapi/issues
https://bitbucket.org/yilmazuur/celestialpay-website/issues
https://bitbucket.org/yilmazuur/celestialpay.me/issues

I couldn't manage to add images here, so this is the link to show some screenshots of celestial wallet:
https://bitbucket.org/yilmazuur/celestialwallet/issues/10/screenshots

WebWallet

So is this some kind of paypal-replacement? Anything to see already?

Asking because we are working on something like that and if a good solution is already about to be released may stop development.

yilmazuur

Yes, that is true. The idea is pretty paypal-like.

WebWallet

yilmazuur just read up a little on bitbucket, looks like it's going a bit different direction to what we plan. How far is the development though? Looks like most still are ideas/todos at this point?

yilmazuur

WebWallet Hopefully mvp for all wallet, api and .me donation capability will be online before this SBC. In couple of days, I think. After this SBC, there will be some infrastructure improvements and new features for next SBC.

At the moment bitbucket items are mostly about infrastructure improvements. There are more going on in my head but I didn't want to spend time on adding items to bitbucket that I might drop later.

There is no harm on having same idea, maybe same use-cases with others. So, Cheers. But, I don't know about SBC's procedure about similar ideas. Maybe someone can enlighten us about it.

WebWallet

There is no problem having similar submissions for the SBC, but I'm not sure how advanced the submission needs to be for it's first version.

yilmazuur

Hi everyone! Apple has rejected my wallet app with this reason: "Your app facilitates the transmission of a virtual currency that is not approved for the App Store." It sucks ?
Anyway, users can download it from celestialpay.com.

Finally, everything is on production.
https://celestialpay.com - celestial website and the place you can download celestial wallet
http://service.celestialpay.com/docs/v1/index - api documentation to request payments
http://celestialpay.me/?uguryilmaz21@gmail.com - donation website which is automatically created for every wallet users, they can use it like this http://celestialpay.me/?registered_email_to_celestial_wallet
I wrote mine as example.

I hope all necessary explanations are already in celestialpay.com

Cheers!

WebWallet

yilmazuur Apple has rejected my wallet app with this reason: "Your app facilitates the transmission of a virtual currency that is not approved for the App Store."

This is known. You should make an APP for android instead. You could also make a "checking app" for iOS to receive notifications when receiving a payment on celestialpay, just remove the option to actually send funds with the app.

yilmazuur

WebWallet Good idea, I can create another wallet for app store regarding this and try it out if apple approves the app this time.

sacarlson

From a quick view it looks your wallet API only supports XLM as an asset? I hope you have plans setup to accept other fiat assets like USD as most vendors need to deal with fiat and can't handle 10% changes in valuation of an asset like XLM every 10 minutes when selling a product or service. Also you might want to think about how multi-sig escrow will integrate into your system. For a web store to be trusted most people need to have a fall back method to get the money back if the vendor fails to deliver. Otherwise I'm looking forward to seeing what your project evolves into. My attempt at a project like yours for an e-store plugin is https://github.com/sacarlson/OpenCart_stellar_plugin that includes a working model of escrow integration as an option and supports any asset the vendor desires as an option.

yilmazuur

@sacarlson Thanks for the feedback and awesome suggestions. I will also check your project.