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

Calvin, thanks for the hard work and creating arb transactions and a use case!

After seeing how these transactions behave, I think I see what the purpose of the "Service" value.  Services, such as your DarkQora/Message Board project can query the Qora chain for specific ATs with specific Service numbers.  This means that you can define a service and filter data at your discretion.  However, since this is an open-service, you will still need to intrgrate some form of validation, since the service field is open, and unregistered.  This isn't a problem but if you want to avoid future service collisions, you should select a service ID that is probably at least greater than 100.

Since you can't claim a service ID, you can specify an ID that others will likely not use.  Also, the community may, in the future, decide to integrate into the Qora communications spec the reservation of services in the lower number range.  These could be control/system serviceIDs, used for some unknown, low-level purpose.

Another way of looking at this value is to consider TCP/IP ports.  If you create an app that needs TCP/IP, there are certain best-practice standards which dictate which ports to avoid because they are considered dedicated to specific tasks (e.g. Port 80=http). Sure, anyone can use these ports for whatever they want, but best practice dictates you shouldn't.  However, if you create your own communications protocol, there are plenty of TCP ports that aren't in common use.  You can use those as you desire.

I recommend the community take the same approach with service IDs.  Let's have a soft-reservation of the bottom 256 and consider anything north of that "free range".

Comments and rebuttals welcomed.

Great news 

agran,

I'm afraid there is a problem with your qora blockexplorer --

It does not show my Type 10 Arbitrary Transaction. (I'm assuming that it just skip type 10 transaction).

Please add Arbitrary Transaction to blockexplorer..

thank you!

Good news!

Just create my very first Arbitrary Transaction --

{"timestamp":1425555747324,
"fee":"1.00001000",
"confirmations":0,
"data":"3aump9mdueoZHMmos2XHYQkpzfBsAQqinvfz",
"service":555,
"type":10,
"signature":"2fZvew21UUj7RfRd7ekc1HWXQq922v1ZwRurSAjE9UGDzfbCkWNGLNX8LgXP3cn5vTzXuLd3pc7u559 9Vg7Lr9aV",
"reference":"2WmAU9tZfphNMtmFkrJnaRBLRy3p1WZCNtdtDQZRZyKWmdxqkEfaQKJiRsKz3cNWmZPFzvsPohCazWT ps4ZnrUA2",
"creator":"QQmwJGqzRBjNMZcQwuzTVhoF4Q9W4QRGPn"}

And this shows up in my wallet under Transaction Tab:

0   Mar 5    Arbitrary Transaction   QQmwJGqzRBjNMZcQwuzTVhoF4Q9W4QRGPn   -1.00001000

Looks like a success!  

Fixed.

No! Don't say that! I really like to hash those ideas out with you.    You've been a big help and not a distraction.    I really appreciate every and all feedbacks because I really want it to be something people will use.

I hope that after the GUI source is released, we will be able to integrate whatever useful service we create into the wallet so they can be used by the whole community (of course they will need to be verified by the Core Dev Team or a chief developer for security and safety reason).  In any case, I'm just getting the ball rolling.    I'd like to show people how simple and versatile Qora platform is.  It's actually very easy to develop applications on top of Qora core.

By the way, there is a function from API does what you just described -- look up transaction scan from the API guide.  I'm going to integrate/implement everything you mentioned into the application.

I actually like your ideas better!    So I'm gonna abandon my original messaging app idea in pursuit of a microblogging type of service. Let's make it into something like a twitter for Qora (don't forget Arbitrary Transaction only allows 4000 bytes data limit)...

So we may not be able to create a long post.. But we can do something like Twitter or Vine.  

First off, a BIG thank you to the two persons who sent me Qora! I've got enough Qora to start my experiment. I'm going to post my result shortly.



I've requested the person in the know to make an official statement regarding the Poloniex situation since it's a common (and valid) concern among the Qora users. I believe it should be addressed by one of the team members.

In case anyone hasn't heard, BTER is planning on enabling withdrawl of all altcoins (perhaps resume trading as well) within one week.  Here's the official announcement from their twitter -

https://twitter.com/btercom



Yes, the dev has been in contact with Vrontis, please see Vrontis' posts.. starting here: https://bitcointalksearch.org/topic/m.10633763

I believe the dev has agreed to fully open source Qora (even release the source for GUI and the native libs), and he even offered to compile the next version of Qora wallet for the community. That's what we've been told.

So has anyone spoken with qora after his return?

What about Poloniex? All my Qora coins are still on the way to Poloniex.

Yes that explain how fast the dev has delivered the coin after the ipo

Qora addresses do look very similar to Bitcoin's and nothing at all like NXT's so I guess it's not surprising.


There are similarities in that both coins are new source, coded in Java, and have a roughly similar feature set, as well as some vague similarities in their devs' postings here but there are also some differences too. As others have said, when BCNext released NXT, he put the whole Java code in a single uncommented file and made use of no additional libraries which is very odd. In contrast, Qora's code is well written and commented.


Link is here:

http://qora.co.in/faucet.php

Last time I used the faucet was two weeks ago and it was working then. It doesn't seem to be working now though.

Hehehe, exactly! This is the proper design to have this working as a form of microblogging - social network.
A subscription service can be implemented into this.I was thinking this like, a service to handle subscriptions and a service to handle posts.Then the client will call the posts made by users that the client's user had subscripted and the posts will be loaded into client's timeline.
To be more specific:

Let's consider service 1 as subscription and service 2 as posts.

The user A uses this client.
The user A have subscribed to follow the user B.
To list this subscription, an arbitrary transaction is needed to be created made by the address of the user A and writes that he listens to user's B posts.

So, the first is a lookup function that searches for the arbitrary transactions made from the address of user A (the same user who uses that client)  in service 1 and gathers the addresses of the users that he had subscribed.This will ensure that the subscription service will not get "hacked" and the client will load only what user A have subscribed by searching for arbitrary transactions made by user's A address.
That's how you build that subscription service and ensure that it will load only what users have desired to have into their timelines.

Then the client scans the service 2 to load the posts made by the addresses that have been gathered from the above function and displays them ordered by time.

Another needed function of that client is a search function in order to let users discover content and/or other users.

I don't want to distract you or redirect you from your original plan (although a messaging service is needed) but I think that we can work this out.

Hey! That gives me an idea... We can actually have a message board inside Qora..

Okay, forget about private messaging for now..

What about a subscription-based microblogging service??  Is that better?

Let's say we will maintain a list of your subscription in the local client (for instance, Vrontis subscribed to calvinstm's blog).

Then, the client will find all the posts (transactions) from calvinstm and display them inside subscriber's client (of course it will require a custom client mod)...

I think that'll be more useful than a messaging service, no?

Let's think about this a bit more before I implement it...

PS: Thanks for the feedback, and gotta say you've got a lot of great ideas, Vrontis. I've gotta think about this too...

If you are planning  to implement a kind of encryption  like Shamir's Secret Sharing you can have a messaging service that supports private messages.

Otherwise the above could be considered as a microblogging service ( and a form of social network   )

Sorry, but I have a small problem.

I tried to get some Qora from agran's Faucet. But it's been 20 mins and I've not seen anything.

Can someone please send me 10 Qora please?  I just need it to test Arbitrary Transaction.

My address is QQmwJGqzRBjNMZcQwuzTVhoF4Q9W4QRGPn, I don't need much just a small amount to pay for transaction fee. (I've got enough Qora for my experiment, thank you!)

Thanks.

PS: agran if you're reading this, your faucet is broken!

An Announcement for Qora Messaging System (Based on Arbitrary Transaction & Will Support Qora Name System)

1. Qora Messaging System has been assigned a Service ID = 1 by me.  I don't know how to restrict use of Service Id, but I hope we can agree that Service port 1 is for messaging and not for other purpose.

2. Qora Messaging System is currently encoded using the Base58 encoder included in the Qora source code.  However, it should support full encryption in the future (after I test it to make sure it's fully working).

3. Qora Messaging System will support "handles" using Qora's Name System.  For instance, if your Qora ID is bob and your partner is matt, bob will be able to message matt directly.

4. Qora Messaging System will support two kinds of targets -- 1) Qora Name-based alias handle, 2) Qora address contact.

5. Qora Messaging System currently has the following data format (will be revised later) -

{recipient:{name or address}, message:{base58 encoded message}}


Let me know if you guys have any input, feature request.. or anything you'd like to add...

Thanks!

Hal,

BTER has always been the primary exchange since Qora's inception.  I believe Qora is not the only coin affected by the recent BTER hacking incident.  But I read somewhere that they're going to reopen the exchange for trading within one week.  So I'm pretty sure Qora will resume trading by then.  So sorry about the inconvenience.    

I don't know about you guys, but I think I'm willing to give BTER another chance since they've proven themselves to be trustworthy (they always stay and find a way to reimburse customers).  As for Polo, I've just been told a dev is handling that situation.  I don't want to speak on behalf of this dev.  If he wishes to provide more information to the community, he will do so.  But I can tell you that I'm confident the problem with Polo will be resolved once the next wallet is released (the latest).

As for Qora's identity (whether he is BCNext or not), I don't think I want to make any conjecture or speculation at this moment (out of respect for the dev), because I know people like Satoshi, BCNext, Qora all have one thing in common - they value their privacy, and we should respect that and not to pry too much.. lol

The truth is I've never bothered to look into NXT's codebase, but I heard that it was pretty messy when JL took over. However, at first glance, my impression of Qora code is that it's very well organized and squeaky clean. It's well commented and very easy to follow.  I don't know if it's an indication that it's two different persons because I'm not familiar with BCNext's style (I know Nxt has been rewritten from the ground up).

Having said that, I can tell you that I've been doing a bit of research, and I can confirm with certainty that Qora is a project that was started back in early 2011 and has been in development ever since.  

That's all I'm gonna say about this..  

PS: Forgot to mention, there is a Qora Faucet created by agran, you can get some free Qora from there for testing purpose.

Thanks...

Sorry I was away getting some work done..

Give me 30 mins, and I'll send the first ever Qora Arbitrary Transaction!     I'll post my result here...

BRB...

There is a big chance for that imho..

I think the only way to achieve that is within the posted data