elective-stereophonic
elective-stereophonic
Show Posts - verymuchso
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - verymuchso

Pages: [1] 2 3 ... 27
1
Nxt General Discussion / Re: Price speculation
« on: November 27, 2017, 10:46:13 pm »
HEAT is doing great!
Would be even better if Lior and Jean-Luc would join our team, I know they love great tech  ;)

2
Nxt General Discussion / Re: Price speculation
« on: November 27, 2017, 08:57:08 pm »
Congratulations guys!
4 years already,

Keep up the good work.

3
I had the pleasure of being interviewed about HEAT by Evan, Christian and Alex from Core TV.

Core TV Episode 05: Heat Ledger (Dennis de Klerk)
https://www.youtube.com/watch?v=dGs2B-0goTI

4
At heatledger.com/ico it currently says you have collected 493 in the BTC account. On the blochchain link, however, the amount is 144 BTC lower. Could you explain the difference?

Total amount BTC on heatledger.com/ico includes all escrow partners (C-CEX, Alcurex and CCEDK/OpenLedger).

6
CORE Magazine August 2016 feat Ardor Platform,
HEAT Ledger, Blockchain News, Radio and TV
(link)



This months issue of CORE Magazine has HEAT on it's cover!
And hosts an interview with the HEAT creators.

https://steemit.com/steemit/@thirdstryker1/core-magazine-august-2016-feat-ardor-platform-heat-ledger-and-blockchain-news

CORE Magazine is made by coremedia.info

8
We are proud to present to you ...

The official HEAT Ledger hand painted - Indonesian roll-cake  ;D









Thanks Marel! For making them  ;)

------

As is shown once again.

HEAT is the FIRST crypto-framework to solve the blockchain size scaling problem.
HEAT is the FIRST crypto-framework to solve the blockchain speed scaling problem.
HEAT is the FIRST crypto-framework with an official Indonesian-Roll-Cake.

Eat that  :D

9
Nxt General Discussion / Re: What Does Nxt Mean To You?
« on: July 25, 2016, 01:34:27 pm »
NXT is what made me specialize in blockchain technology.
NXT taught me how to build crypto platforms.
NXT was the basis for FIMK.

NXT was the blueprint for HEAT (dressed down and rebuilt from the ground up)

NXT is a lot of fun!

10
I would like to see a client before investing. But the client was planned after the ICO.

We have an amazing client platform. (sounding like Trump here almost)
After having worked on Mofowallet for some time which was really basically my first ever web app (had to learn Angular for that) we now took it to a whole new level with Angular 2 typed coding completely written in TypeScript and using Google Material Design.
Its completely web component based and comes with probably the nicest ever ordering of crypto-graphic routines and services you could ever want .
Everything is real-time and uses websockets.

I'm pretty sure the NXT devs will have as much fun with our client framework as we had with the NXT server framework.  ;D (hint ... since its pretty much compatible to NXT API)
How great to help each other out right!

11
I'm just a simple developer, I'll happily answer all tech related questions.

Quote
HEAT slices the currently used blockchain database technology to modular components
I'm not a dev so I don't understand how this happens. It sounds like a "modified" blockchain. Like you are changing the fundamental structure of the typical blockchain. Is that the case? Can you go into a bit more detail keeping in mind I (and others) are not software developers?

What it means is that we have a blockchain structure that allows us to slice it in pieces.

Unlike NXT we dont use a standard database (NXT uses the H2 java db, ETH and BTC use LevelDB etc..) with tables and columns and indexes and all that stuff.
Instead HEAT blockchain data is placed sequentially in files where we start with all the block details and then a multiple of transactions that go in that block, then a block and so on and on.

This structuring allows us to scan a full chain of 5 million transactions in just seconds (other optimizations where needed for this but i'll leave them out now), while in NXT this would take up to a day at worst or many many hours at the least (this is not since NXT is slow, try scanning the bitcoin chain).

The NXT database also keeps tracks of all balances, there are account balances, asset balances but also order balances (how much of your order is eaten) with NXT all that goes in the same H2 database.
HEAT has created custom storage solutions where we have a storage for account balances, unconfirmed balances, guaranteed balances, asset balances, order balances etc etc (doing this from the top of my head).

The big advantage of building custom tailored storage for those things is that we basically do what SQL and H2 does for NXT, yet extremely optimized, using open source components borrowed from the HFT industry. We can read many many millions (30 million plus) balances a second where with a database you only get to do standard crypto currency speeds.

A really really big part of the NXT source code goes into all the H2 database hand-lings (which we've all removed - so please don't dismiss us as 'just' a clone) while structurally very smart (Jean-Luc basically taught me crypto system architecture  ;)) all those 'solutions' like rollbacks, derived tables, trimming etc all build on SQL and SQL transactions.
All of that we needed to write custom solutions for, all the way up to system crash recovery which in NXT is solved basically by H2 db.

But now to the fun part.. After HEAT has run for a while and our blockchain has grown to about 1 or 2 GB..
We start a new file and we'll be storing blocks and transactions in that new file and people only need that last file and dont need the transactions or blocks that have gone in previous blocks files.  8)
What is needed to be able to validate that last blockchain, without having access to previous transactions... are the balances that came out that previous blocks file.
The nice thing here is that while a blocks file might be 1.5 GB. The balances coming from that are just a few MB. (i'll leave the details for later - but key here is a combination of balance checksums combined with expected before and after scan balance numbers).

PS (1). Some might ask ... if there is no db ... how do you provide deep data analytics to power advanced clients/cloud api hostings/wallets?
The answer to that is our replication layer, its where we optionally and in real-time sync everything and more that H2 knows about in NXT.
But in the case of HEAT to a much more powerfull MYSQL database (this comes out of the box) or if you choose so to a super sized storage like dynamodb to power really serious user levels (decentralized Facebook anyone).
And in HEAT the consensus parts has nothing to do with the replication or view parts (its basically what they propose here: http://fc16.ifca.ai/bitcoin/papers/CDE+16.pdf - funny to see how we came to the same conclusion).

PS (2). This same replication mechanism allows us to present a real-time status of all orders, confirmed or unconfirmed which again works great to power our AE UI which basically works as instant as for instance poloniex or any other exchange does (we can discuss this later if anyone wants).

Quote
users can trade cryptocurrencies right from their wallet on p2p orderbooks without going through an exchange.
Provided they are trading with others on HEAT is that correct? Is this like taking a USD out of my pocket and giving it to someone who gives me a Euro? If we are trading wallet to wallet is there a fee?

Not sure where but I've mentioned my idea on this forum once before (lucky no-one developed that further) but HEAT comes with Decentralized Services Architecture.
Call it luck but I've used to do be quite active in the field of building scripting solutions that integrated inside Java applications (thats probably what lead me to the idea).

What Decentralized Services Architecture is in its simplest form is that you write a Javascript (or TypeScript - thats what i do - so in love with TypeScript lately) which you simply drag/save in a special folder inside your HEAT installation. This script then registers as a listener for blockchain events (we use Java nashorn for that - but anyway) but the script will not run everytime a new transaction comes in. The script itself knows what account its working for.

Users anywhere in the world can create a transaction with a special structure and send that to the service account (we have client software that automates all this - even the UI is generated) , the script now runs and does what it needs to. This even involves talking back (and forth etc) with a customer.

To give an example:

Alice is a service provider, she exchanges BTC for ETH. You send her BTC and she'll send you ETH.
Now BOB calls to Alice her service, bob knows what params are needed since Alice advertises that on the chain.
Bob sends his BTC amount and his ETH recipient address (as message attached to a transaction with recipient Alice).
Alice now replies, taking in the BTC amount Alice lets Bob know that he will get X ETH and that if he wants to he needs to send the amount he proposed (of btc) to BTC address Y.
Bob in turn does what Alice requests and could optionally send another message to Alice (over the chain) that he send that BTC combined with the transaction id.
Alice now has her bot look up the best price for ETH on polo or any other exhcange, or she has it herself, she exchanges the BTC Bob send and she sends him his ETH.
Alice is a service provider so she definitely sends proof back to Bob which includes the transaction id.

Voila we have a truly decentralized Shapeshift now  ;)

Yet all transactions (and thus reputation) of each service provider can be confirmed through going over all transactions she send and received.

Sounds complicated (which it is) but distilled to its bare essentials and using a nice Javascript lib who handles things under the cover, writing services actually becomes dead simple.
And its even easier if service providers publish their service code (in order to get more trust) which anyone basically can copy.

Yeah its a head spinner I know, but it works and it can be used for millions of things.

1. Buying on Amazon
2. Renting movies
3. Exchanging currency etc etc

Distributed Services Architecture is what I personally like best, it can truly grow into a whole new economy on itself   :D

What will be the incentive for Java software developers to use HEAT? How are DSAs > dApps?

DS (distributed services) are written in javascript or java but why use Java? For DS JS or even better TypeScript is way better.
But if you want to make use of our blockchain as a way of safely storing your data, yet want to write custom replication plugins to interpret your data and feed that into your custom MySQL or Progress models, Java is your friend (or Scala, Clojure, JRuby .. what ever tickles you).
With HEAT that is totally possible.

I asked a lot of questions and I hope none offend. I'm sure others are wondering the same things. I look forward to your response :) Thank you

No problem  :D

12
Transparent Forging / Re: start forging of forged Nxt
« on: July 05, 2016, 03:00:41 pm »
So when I forge NXT those will help me forging instantly, right?

Wrong!

Forger fee is added to balance in the same way as regular payments in transactions are applied.
Which means they will go through Guaranteed Balance and stay there for N+ blocks before they add up to form effective balance.
What is updated immediately is something called "Forger Balance" but this is just fluff, has no functionality in the core validation process.

@See: https://bitbucket.org/JeanLucPicard/nxt/src/bc2c2527791ac16bad75d9df0fc0013acd02537e/src/java/nxt/BlockImpl.java?at=master&fileviewer=file-view-default#BlockImpl.java-393

If this where to somehow be allowed the whole point of letting balance sit for N blocks before they can be used to attack the consensus would fail since you could just send yourself funds through ridiculously high fees for transactions.

13
Nxt General Discussion / Re: [TNNSE] Tennessee Updates
« on: May 31, 2016, 06:40:25 pm »
Honest review:

Bas nailed it.
He's a very talented speaker, the way he talks about NXT is mesmerizing.

Tosh is younger, which shows.
But I'm really impressed by his presentation skills the way he brought the story from stones on islands far away and hundreds of years ago straight back home to bitcoin.
Very impressive and for a German, his English is outstanding.

Who knows .... this NXT thing, could be huuuuge one day with folks like these  ;D


14
Nxt General Discussion / Re: [TNNSE] Tennessee Updates
« on: May 31, 2016, 06:26:12 pm »
http://imgur.com/a/IHtGj
these are the pics posted to meetup.com

Edit: Seems like I'm even in one  :D

15
Nxt General Discussion / Re: [TNNSE] Tennessee Updates
« on: May 31, 2016, 06:21:51 pm »
How was the DEV070?

I enjoyed it.
Bas, Tosch and Henk all gave interesting talks.
Also enjoyed meeting Dave and Lior. Hi guys!

Any pics or video coverage?

It seemed like the whole thing was taped.

16
Nxt General Discussion / Re: [TNNSE] Tennessee Updates
« on: May 31, 2016, 05:16:56 pm »
How was the DEV070?

I enjoyed it.
Bas, Tosch and Henk all gave interesting talks.
Also enjoyed meeting Dave and Lior. Hi guys!


17
NXTPortal.org / Re: nxtportal.org - Nxt blockchain explorer
« on: April 19, 2016, 03:51:27 pm »
For partial RS accounts I think I'd need to query the db directly but I'd prefer to use the API.

Account id's are stored as unsigned longs in the db.
The rs addresses are calculated from those longs.
You need to add an extra table to store the RS ids or you should write some java plugin that stores the RS address with each new address in for instance the account_info table.

In FIMK an extra table was added, it's also what we use for send money recipient auto complete suggestions.

https://lompsa.com/#/search/fim/accounts/abc

18
Democracy Counts! / Re: Introductions & Join ups
« on: April 15, 2016, 12:13:18 am »
I have a pulse  ;D

And am reading the whitepaper devlux send me over email.
It's an interesting read, somewhat rough, but i'm sure there are many here on this forum that like the technical details laid out in the paper.

Great initiative guys!

19
Nxt General Discussion / Re: Experience with forging on Azure?
« on: April 13, 2016, 12:25:24 pm »
Could somone explain to me how does azure BAAS work?
Is that using docker or have they come up with their own template thingy?

I understand the marketing value of the first cryptos who "partnered with Microsoft" (not such a big deal if you look beyond the headline).
But isn't https://www.openshift.com/ offering the exact same thing?

~ ~ ~

Was there no talk of a docker container setup on this forum ages ago?
Sounds like something for nxt.org to host with some easy steps to deploy on AWS, Digital Ocean, open shift whatever.

(extra free tip: nxt.org organization could earn money from the referrer links to those cloud hosters).

20
More participation is always good imo.

Absolutely. But at the same time many societies have grown accustomed to democratic elections being undecided until the counting starts.

We are guessing here of course, since we have not heard the details of the system in place yet.

But if the real-time vote observing is a possibility here you can't deny this brings a whole lot more change to the table then just creating a tamper proof mechanism.

There are methods of course where you can observe voter turn out in real time, but not reveal the outcome of those votes until the counting normally starts.
Blockchain tech and especially public/private key cryptography are the things that allow this.

Pages: [1] 2 3 ... 27
elective-stereophonic
elective-stereophonic
assembly
assembly