Pages:
Author

Topic: Qora | 100% POS | Assets | Names | Voting | Open Source - page 14. (Read 113830 times)

legendary
Activity: 1470
Merit: 1024

 sorry guys. would anyone send me some qora? Not much. i just wanna try to deposit in my wallet if it works.

 QPk9aqLmP7wEqSzNTMZNXpnxojJxEPfeFP

 Thank you.
legendary
Activity: 1708
Merit: 1000
Reality is stranger than fiction
Counterparty used burning too.. and it had a good ROI
full member
Activity: 201
Merit: 100
Wow this is all incredibly good news.  Thank you and welcome to our new developers!

I have an idea regarding the Qora services that I think could be a big deal for Qora's future.

In some other coins, there is the concept of having the blockchain be profitable.  For example, in Ripple, Bitshares, and NXT (3 of the top 10 coins), there are ways in which the currency is burned forever when the services of the blockchain are used.  (There are also ways to pay dividends or yield on assets within the system, as another way that profitable enterprises can run in the blockchains.


My idea for QORA is: what if some percentage of the QORA which was spent on these services that we develop was burned forever, thus reducing the QORA supply permanently? 

Even if the burned amounts are very small, this could generate a lot of excitement for the coin.  This is the entire value proposition behind XRP (the ripple coin), as small amounts of XRP are burned whenever ripple is used.  The idea of a deflationary, profitable coin is something that gets a lot of people very excited, and should gather us more support for QORA.


How I imagine this would work is:
There is a community standard that 10% (or some amount) of all payments for the QORA services are permanently burned. 

This percentage could be configurable such that the person running the service could set the burn rate (higher burn rates would be more attractive to the QORA community, but if they person needed to burn 0% thats fine, as long as people support them).  Alternately, it could be a fixed amount like 10%.

Service providers could either slightly raise their price, or just accept getting slightly less QORA, knowing that the process was very good for QORA itself and was increasing the value of their coins.



What we would need:
* A way for QORA to be burned permanently.  Does this exist in the code?
* Code for service providers to set the burn rate of their service.
* Community agreement that this is a good idea, and agreement on what the standard burn rate is, or whether it is up to the service provider.  (We could all vote on this in the voting system).


Do you all like this idea?  Especially devs working on services, are you opposed to this, or do you like it?  We definitely do not want to implement something liek this if it would alienate our developers.


If this is implemented, it could be a powerful idea for us to market to the crypto community to gain more QORA supporters.
hero member
Activity: 521
Merit: 522
Developer - EthicHacker - BTC enthusiast
i am happy to believe and trust to Qora. it was bottom when i met qora but i believe its potential and it ll increase day by day

Hello QORA-user and QORA-team,

the potential is very big. and with a team which work together, share idea together and MAKE THING HAPPEN TOGETHER. then the limit is nonexistent. I looked for many projects in last weeks, and have soo big interest for helping a coin and go in a OS community and cryptocurrencies project because i have big faith in the soul of OS. So now i find the a good project to also help! thank you for this chance in this project.

i will put all things i make for qora in: https://github.com/ca333/qora/
also you can see my other projects i make or see my posts in bitcointalk so you see what is my interest and hobby.
i have graduated from ETH zurich and have deep knowledge in many fields of IT most i work in networkrealted projects and cryptography.
one from my new projects is satoshihack.com, bitcoinhackme.com and bitcoinhack.com under the project satoshislab.com. my project goal for this is here: https://bitcointalksearch.org/topic/hackathon-satoshihackcom-the-first-opensource-bitcoinhackme-993678
and i will make it now in the first hackathon for BTC and QORA in satoshislab.com - so i bring more and more skilled people from IT with more knowledge in various IT-fields in the crypto-community.

thank you!
ca333

legendary
Activity: 1470
Merit: 1024
i am happy to believe and trust to Qora. it was bottom when i met qora but i believe its potential and it ll increase day by day
hero member
Activity: 502
Merit: 500
Wow, I am really excited about what is going on here! Now, with skilled developers and people with ideas, we can make the world understand the true potential of Qora. You guys have my full support!
newbie
Activity: 47
Merit: 0
So I'd like to share a great news with the community.

I've just had the most interesting talk with scriptmastr, and I'm happy to announce that we've got two extremely talented developers from Switzerland joining the Qora team!

(Sorry i forgot your friend's ID.. is it cs333?  Tongue)

Anyways, I think you're extremely talented and very happy to have you guys on board! I'll let you guys introduce yourself.  Smiley

Regards  Smiley



thanks for the kind and motivating words. my collegue is ca333. he s a very active and skilled developer and i am sure that he ll be an enrichement for this project. very excited about the future of the project and very optimistic regarding this dev-team as well as this community. thanks for the opportunity to join it!
full member
Activity: 229
Merit: 101
So I'd like to share a great news with the community.

I've just had the most interesting talk with scriptmastr, and I'm happy to announce that we've got two extremely talented developers from Switzerland joining the Qora team!

(Sorry i forgot your friend's ID.. is it cs333?  Tongue)

Anyways, I think you're extremely talented and very happy to have you guys on board! I'll let you guys introduce yourself.  Smiley

Regards  Smiley

newbie
Activity: 47
Merit: 0
First, remember, these can't be "reserved" only "preferred".  Second, I recommend that you use number of 1,000 or higher, ask suggested bt CIYAM and myself earlier.  This is so that these IDs can be resevered and used in a more-official sense in the future.

My .02 cents on it.  You can do whst you want to do, but after working in IT and with communications for years, I can say that "cherry picking" lower IDs (which is how this could be perceived) is a little unprofessional.

Please understand, I'm not hassling you, but trying to educate/advise on the situation and explain why I don't support using those values.

Okay, I agree.  Cheesy  I've got no problem with that.. So we're reserving lower 1000 IDs (from 1 to 1000) for core use???

Then I think I'll take 1000 to 1200 then (I'll need to revise my app, but thankfully, I haven't really uploaded too many transactions yet).. IF there is no objection.. Thanks for the feedback, btw.. Really appreciate it!
agree. i ll take ID 1201-1221

btw i am working out a php API wrapper to allow wider adoption and also give other webdevs and supporters the chance to launch own qora-services. i miss a mobile wallet so thats the first thing i am going to build upon my API lib.

i ll opensource all of my work. and i ll post updates here as well as on the site which will be hosting the mobile wallet.

check it out! http://qora2go.pw

please support this project and donate some QORA


Sent 2m qora to you.
Wish you can do better.
If you have any idea or something about crypto , you can pm me. I am working coinport which focus on bitcoin payment.

oh wow! thanks a lot for this generous gesture. i really appreciate it. i am glad to be part of this yet young but so innovative and promising project! i ll drop you a message later on.
and thanks again!!
sr. member
Activity: 422
Merit: 250
First, remember, these can't be "reserved" only "preferred".  Second, I recommend that you use number of 1,000 or higher, ask suggested bt CIYAM and myself earlier.  This is so that these IDs can be resevered and used in a more-official sense in the future.

My .02 cents on it.  You can do whst you want to do, but after working in IT and with communications for years, I can say that "cherry picking" lower IDs (which is how this could be perceived) is a little unprofessional.

Please understand, I'm not hassling you, but trying to educate/advise on the situation and explain why I don't support using those values.

Okay, I agree.  Cheesy  I've got no problem with that.. So we're reserving lower 1000 IDs (from 1 to 1000) for core use???

Then I think I'll take 1000 to 1200 then (I'll need to revise my app, but thankfully, I haven't really uploaded too many transactions yet).. IF there is no objection.. Thanks for the feedback, btw.. Really appreciate it!
agree. i ll take ID 1201-1221

btw i am working out a php API wrapper to allow wider adoption and also give other webdevs and supporters the chance to launch own qora-services. i miss a mobile wallet so thats the first thing i am going to build upon my API lib.

i ll opensource all of my work. and i ll post updates here as well as on the site which will be hosting the mobile wallet.

check it out!

please support this project and donate some QORA


Sent 2m qora to you.
Wish you can do better.
If you have any idea or something about crypto , you can pm me. I am working coinport which focus on bitcoin payment.
full member
Activity: 229
Merit: 101
agree. i ll take ID 1201-1221

btw i am working out a php API wrapper to allow wider adoption and also give other webdevs and supporters the chance to launch own qora-services. i miss a mobile wallet so thats the first thing i am going to build upon my API lib.

i ll opensource all of my work. and i ll post updates here as well as on the site which will be hosting the mobile wallet.

check it out!

please support this project and donate some QORA


Totally Awesome!!  Extremely Excited to have you on the dev team!!  Grin Grin  

By the way, to me, I feel it's entirely possible to build fee-based services at the moment (so if anyone wishes, they can turn it into a business).  Right now, I am doing the development in Java but will love to learn more about your work.

What do you think of the Qora App Store idea?  Smiley  I was thinking maybe eventually people will choose Qora Services Explorer as the launcher of choice for their app (they can get paid by setting an optional service fee).

Anyways, as it stands, I am thinking maybe we should agree/develop a framework that will serve as the basis for the Qora App Store (launching platform).. Maybe the developers should work out a standard platform where services will be launched.  I don't know.  Smiley

Gotta run now, But will love to hear more about your thoughts and your visions.  Thanks for being here!  Smiley
full member
Activity: 229
Merit: 101
Before I get back to work, I'd like to share a very important message with potential developers who are looking to develop 3rd party apps for the Qora platform.

1. Right now it's entirely possible to build fee-based applications on top of Qora that will provide a steady stream of income!  The way it works with Qora Services Explorer is like this --  every time an user launches an application, an (optional) fee is paid to the developer at launch. So think of it as a SaaS (Software-as-a-service) platform.  My goal and vision for Qora Services Explorer is to eventually turn it into something like a "Qora App Store" where developers can list their applications for end users.  My only goal and objective here is to help attract 3rd-party developers to Qora. So if anyone has any question or just want to learn more about developing for Qora as a business, I'd be happy to share my insight and what I've learned. Just post your questions and I'll help answer it.

2. What makes Qora the ideal platform to build your fee-based applications on is the following - Qora is a very stable and mature system that have been in development since 2011 and is fully open sourced at the moment (even the native c libraries and graphical user interface codes have been released by the developer).

Qora has lots of tools and features set to build your ideal applications (Arbitrary Transactions for Data and upcoming Automated Transaction for Scripted Automated Processing) - plus an entire suite of API calls at your disposal.

Another thing is Qora is very well organized and neatly commented. It's very easy to learn anything you want about Qora simply by following the code.  Smiley  To me, Qora is one of the best development platform in the market today.

Thank you!!  Cheesy
newbie
Activity: 47
Merit: 0
First, remember, these can't be "reserved" only "preferred".  Second, I recommend that you use number of 1,000 or higher, ask suggested bt CIYAM and myself earlier.  This is so that these IDs can be resevered and used in a more-official sense in the future.

My .02 cents on it.  You can do whst you want to do, but after working in IT and with communications for years, I can say that "cherry picking" lower IDs (which is how this could be perceived) is a little unprofessional.

Please understand, I'm not hassling you, but trying to educate/advise on the situation and explain why I don't support using those values.

Okay, I agree.  Cheesy  I've got no problem with that.. So we're reserving lower 1000 IDs (from 1 to 1000) for core use???

Then I think I'll take 1000 to 1200 then (I'll need to revise my app, but thankfully, I haven't really uploaded too many transactions yet).. IF there is no objection.. Thanks for the feedback, btw.. Really appreciate it!
agree. i ll take ID 1201-1221

btw i am working out a php API wrapper to allow wider adoption and also give other webdevs and supporters the chance to launch own qora-services. i miss a mobile wallet so thats the first thing i am going to build upon my API lib.

i ll opensource all of my work. and i ll post updates here as well as on the site which will be hosting the mobile wallet.

check it out! http://qora2go.pw

please support this project and donate some QORA
full member
Activity: 229
Merit: 101
First, remember, these can't be "reserved" only "preferred".  Second, I recommend that you use number of 1,000 or higher, ask suggested bt CIYAM and myself earlier.  This is so that these IDs can be resevered and used in a more-official sense in the future.

My .02 cents on it.  You can do whst you want to do, but after working in IT and with communications for years, I can say that "cherry picking" lower IDs (which is how this could be perceived) is a little unprofessional.

Please understand, I'm not hassling you, but trying to educate/advise on the situation and explain why I don't support using those values.

Okay, I agree.  Cheesy  I've got no problem with that.. So we're reserving lower 1000 IDs (from 1 to 1000) for core use???

Then I think I'll take 1001 to 1100 then (I'll need to revise my app, but thankfully, I haven't really uploaded too many transactions yet).. IF there is no objection.. Thanks for the feedback, btw.. Really appreciate it!

PS: Just re-read your statement, I understand where you're coming from, but I think we should definitely set up a reservation system and strictly enforces it for the reason outlined above -- Let's say if a developer doesn't check data format and just process data blindly, it will break an application and lead to bad user experience, don't you agree?  Smiley  (And I think it will happen very often)

BTW - thanks for playing the advisor role, definitely appreciate it!
rlh
hero member
Activity: 804
Merit: 1004
First, remember, these can't be "reserved" only "preferred".  Second, I recommend that you use number of 1,000 or higher, ask suggested bt CIYAM and myself earlier.  This is so that these IDs can be resevered and used in a more-official sense in the future.

My .02 cents on it.  You can do whst you want to do, but after working in IT and with communications for years, I can say that "cherry picking" lower IDs (which is how this could be perceived) is a little unprofessional.

Please understand, I'm not hassling you, but trying to educate/advise on the situation and explain why I don't support using those values.

Great work, btw!  This is really a good thing to add into qora.
full member
Activity: 229
Merit: 101

It's awesome.

Thanks for the support! Btw, I really think you should talk to Vrontis about his project. Right now, he's working on a Node.js based webapp wallet for Qora, and I feel you've got a lot to contribute.  Maybe you guys can team up and collaborate on something together.

Let's make Qora the most successful Crypto Ever!



i d like to reserve port #110 - #160. and btw - great work!
going to announce my work later on. keep it up guys!

Glad to see new developer joining the team!  I think eventually we need to merge our work together and create an "Unified Qora Services Repository" for the end users. I'm going to share my visions and outline the direction we should take in my next post.


I'm very happy & excited to see people implement services using Arbitrary Transactions.

I agree with the reservations - FTTB it's first come first served approach.

I was just wondering about the following 2 things:

  • The first x slots (1 to 9 and 101 to 109) will be used for some more core/central function or they are reserved because of some reason?
  • If someone decides to use one of the already defined ports/ would he be able to create problems? If yes, how can we overcome it / could we add one extra form of authentication?



I'm going to answer your questions backward -

2. I feel reservation is absolutely necessary, and it's a very bad idea for another person to use a "reserved port" for another use (unitended).  The reasoning is very simple -- If a developer create an application that process data blindly (meaning - not checking if the data conform to certain standard or format), "Bad Data" will definitely break the application and lead to negative user experience.  We certainly don't want that, do we?  Smiley  And you know, it's really easier for developer if a port is considered reserved so he doesn't need to perform "Data Check" for every block he comes across. Just my 2 cents.  Smiley

1. Between rlh, CIYAM, and me, we were just discussing how the reservation system should work.  And I just wrote a post saying that I agree with rlh - maybe we should reserve lower number ports for CORE USE and leave higher ports for 3rd party application.

There is no built-in reservation system that restrict any Service ID for 3rd-party use, but I definitely think we need some sort of written system to regulate Service ID (prefer to call them ports) use.  
legendary
Activity: 1708
Merit: 1000
Reality is stranger than fiction
I'm very happy & excited to see people implement services using Arbitrary Transactions.

I agree with the reservations - FTTB it's first come first served approach.

I was just wondering about the following 2 things:

  • The first x slots (1 to 9 and 101 to 109) will be used for some more core/central function or they are reserved because of some reason?
  • If someone decides to use one of the already defined ports/ would he be able to create problems? If yes, how can we overcome it / could we add one extra form of authentication?

TIA,
wizzardtim
newbie
Activity: 47
Merit: 0
A little introduction and some quick note regarding Qora Services Explorer:

1. If there is no objection from the community, I'd like to reserve Service ID #10 - 100 for my personal development purpose.

2. Basically, the drop-down list contains a list of Services that are available to the end Qora users - Currently there are only two working services, but I plan to add more:  MicroBlogging Service at Port 10, and Qora DarkNet (Hidden Web Service) at port 20...

3. Eventually, I plan to integrate a full node browser.

Feedbacks & critiques are always welcome.  Grin



In case anyone is interested, this is the Qora project I've been working on in my spare time:

Qora Services Explorer (with custom Qora Wallet), below you will find a screen capture..


http://i.imgur.com/n4P3E9h.jpg

i d like to reserve port #110 - #160. and btw - great work!
going to announce my work later on. keep it up guys!
legendary
Activity: 1806
Merit: 1001
A little introduction and some quick note regarding Qora Services Explorer:

1. If there is no objection from the community, I'd like to reserve Service ID #10 - 100 for my personal development purpose.

2. Basically, the drop-down list contains a list of Services that are available to the end Qora users - Currently there are only two working services, but I plan to add more:  MicroBlogging Service at Port 10, and Qora DarkNet (Hidden Web Service) at port 20...

3. Eventually, I plan to integrate a full node browser.

Feedbacks & critiques are always welcome.  Grin

It's awesome.
legendary
Activity: 1806
Merit: 1001
The new logo is already finished, but Bitcrea doesnt release the logo, until he can acces his funds on Polo.

May ask I who made the decision to change the logo and website? To be honest I'm kinda worried about it. 9 times out of 10 people change something just for the purpose of change itself and it always hurts the product. I mean, nobody even saw the new logo, but it announced like final decision and so on. The same goes for the website.
Pages:
Jump to: