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.


Topics - warmach

Pages: [1] 2 3
1
General FIMK Discussion / What's next?
« on: Today at 02:40:14 PM »
I know HEAT development is still ongoing, but what is in the future of FIMK? 

2
General FIMK Discussion / Forging Service - Anyone Interested?
« on: November 12, 2016, 03:00:30 PM »
As we see our network stability becoming an issue, I'm trying to think of ways to help.  As we've determined, the instability is likely because we don't have a large number of forgers. 

I have an idea to help with that.  Before I write the code to make it happen, I wanted to ask the community if they wanted it and/or if it would be helpful.  Please respond with your feedback.

My idea is to do away with a forging pool and become forging service instead.  Each "client" would be given their own forging address.  The password to this address would be held by my service and the client.  The client would then lease their balance to their own forging address.  My server would then forge using the forging address.  After a set period of time, probably 24 hours, any forged funds would be transferred back to the client's original address. 

With this method, my pool would add another 15-20 forgers to network.  With both parties having the password to the forging account, trust required in the service is reduced as the client has direct access to their forged funds. 


3
Technical Discussion / Chained leasing
« on: August 29, 2016, 05:36:05 PM »
Does the forging algorithm allow chained forging balances? 

For example

Account A has 500 FIM and leases to Account B, that has 250 FIM. 

Account B leases to Account C.  When Account C forges, does it forge with just the 250 from B, or 750 from A and B

4
FIMK Client discussion / Lompsa Feature Request
« on: July 26, 2016, 04:04:45 PM »
I am not sure if Lompsa development is going to continue or will be merged with HEAT.  This feature request also applies to HEAT.

My feature request to allow the client to "watch" one or more accounts.  Most of us have a few accounts and it is helpful to be able to see all of them in a combined dashboard.  We can then login to each as necessary to do what we need.


5
General FIMK Discussion / FIMK and NXT 2.0
« on: June 02, 2016, 01:42:09 PM »

FIMK has typically followed the NXT development and incorporated those changes into the protocol.  With the announcement of NXT 2.0, does that change the previous FIMK development cycle at all? 

6
Looks like CCEDK will be shutting down website and trade engine at the end of May.  They will then be relaunching new services and website on July 1

http://bitscan.com/articles/ccedk-evolves-the-decentralized-conglomerate


7
Technical Discussion / Node mapping
« on: May 11, 2016, 04:15:43 AM »
I was working on a script to map out the nodes on the FIM network.  The easy way is to just hit my local node API and getPeers.  I then do the same thing for each of those peers.  Repeat. Repeat. Repeat.

But what if the node has the API turned off.  Isn't having the API server off the default setting?  What about connecting to each server via 7884?  Do I have to use websockets?  Or can i GET/POST?  What kind of function calls are available on that port? 

I've only ever worked with the API on 7886.

Thanks!

8
FIMK Markets and trading / Warmach's OpenLedger Gateway Closed
« on: April 16, 2016, 12:50:54 AM »
I have decided to close down this gateway.  The biggest reasons are low volume and the current legal environment regarding cryptocurrency in my home country. 

If you would like to pull your FIMKRYPTO out of OpenLedger, please follow the standard withdraw routine...

Transfer your FIMK out of OpenLedger
     a.  Transfer your FIMKRYPTO asset to my asset owning account, "warmach"
     b.  Include your FIMK network address in the memo field where you want the FIMK transfered

I will allow about two weeks for withdrawals to be requested.  After that, I will take remaining balances greater than 1 FIMKRYTPO and issue FIMK asset as a replacement. 

Here are the balances as of the closing of this service.

https://imgur.com/a/FZ2PS





In an effort to create a little diversity in FIMK exchanges, I've created an asset (FIMKRYPTO) on the decentralized exchange OpenLedger.  There will be a 1:1 ratio between asset and FIMK.

OpenLedger uses Bitshares 2.0 and the Graphene technology to create a truly decentralized exchange.  To use the exchange, you use one of several "gateways" to transfer in/out funds.  I will be acting as a gateway between the FIMK network and OpenLedger

You can find out more specific details about OpenLedger and it's underlying technology here, https://openledger.info/?r=warmach20

Here is the info page on the asset, http://cryptofresh.com/a/FIMKRYPTO

Why Should I Participate?

The OpenLedger decentralized exchange provides a variety of assets and currencies available for purchase or sale.  Any of these products can be used to purchase FIMK on the exchange.  In addition, as it is decentralized, there is no central authority that can be hacked or defrauded.

What is Warmach's involvement?

Right now, the asset on OpenLedger is created and managed by me, Warmach.  This is a simple way to provide a mechanism for representing FIMK on the exchange.  Unfortunately, I don't have the time or resources to create a SmartCoin on OpenLedger which would decentralize things a little more.  This may be an option in the future depending on the success of this venture.

Why Should I Trust You?

Trust here is important.  You are trusting me to accept your FIMK and give you the OpenLedger asset.  You are then trusting that I would then give your FIMK back upon withdrawal. 

I have been a member here and supporter of FIMK since the IPO.  I've been active on the forums and am running a forging pool that started in July 2015.  I have a vested interest in seeing FIMK's success.  Please feel free to look at my forum posts and PM any of the prominent forum users to ask about me. 

How Do I Participate?

1.  You must first create an OpenLedger account.  https://bitshares.openledger.info?r=warmach20
     * Please use provided link so that I get referral credit

2.  Transfer your FIMK you wish to put into OpenLedger
     a.  Memo field must contain your OpenLedger account, i.e. warmach20
     b.  Send the FIMK to FIM-JL82-GQ4R-ZGGF-66KDD

3.  Conduct your trades via OpenLedger


4.  Transfer your FIMK out of OpenLedger
     a.  Transfer your FIMKRYPTO asset to my asset owning account, "warmach"
     b.  Include your FIMK network address in the memo field where you want the FIMK transfered

How Much Does This Cost?

All market trades have a 0.3% fee that goes to issuer.  These fees are subject to change.  There is also the 0.1 FIMK network fee for all transfers.  I will probably have the storage account forge on my pool and use these funds to cover the network fees.

What Future Plans Do You Have For This Project?

Right now, this process will be manual.  If you want to expedite the transfer, send me a PM and I will do it as soon as possible.  I have a script to monitor the account and notify me of necessary transfers.  For now, I would still like to manually check transfers before executing them.

But if there is sufficient interest in this service, I plan on....

1.  Creating a website that will easily show the usage and transactions of the service on the FIMK network and OpenLedger
2.  Automate the transfer of funds between the two systems so that it happens more quickly with less human involvement.


A very simple tutorial is here with some screen shots on using OpenLedger.  http://fim.warmach.info/trading.html

Please feel free to provide constructive comments.

9
General FIMK Discussion / Thanks Zero Pool!
« on: April 04, 2016, 03:29:25 PM »
Zero Pool contributed some FIM to each forger on the network.  I know each of us appreciate the recognition in supporting the network!

 :thumbup:

10
General FIMK Discussion / Long Block Times
« on: March 21, 2016, 10:00:03 PM »
What is going on with the network lately?

I post a transaction and my client and online Lompsa site both take forever to get a confirmation.  I routinely don't have new blocks for 500+ seconds.  What is the deal?  The network nodes arguing over which blocks are the correct ones?

Any one else see this?

11
FIMK Markets and trading / OpenLedger Decentralized Exchange
« on: March 11, 2016, 08:51:24 PM »
Would anyone be interested in trading on OpenLedger decentralized exchange?

https://openledger.info/?r=warmach20

I would be happy to create an asset on exchange and act as pass through/gateway from FIMK network to OpenLedger exchange.  I've already done a similar thing for Timekoin.  I would rather not spend the time and money to do so if no one is interested. 

Thoughts?

12
Technical Discussion / Prunable Messages
« on: March 05, 2016, 03:26:27 PM »
I was going to setup some automated AM messages to be sent.  These messages do not need live on the blockchain forever.  Is the Prunable Message feature implemented in the current server? 

13
General FIMK Discussion / Fork?
« on: January 11, 2016, 11:14:17 PM »
Do we have a fork out there?

I noticed my client was behind the Lompsa block count by about 1500 blocks.  When I looked at the log, I saw that it was generating about every block.  Obviously I was on my own fork.  I shut down the machine, wiped the FIM server code then re-installed 0.6.0 server.  I also used the DB download from Eliphanz as a start to the DB.

Once I started it back up, its forking again... is it just my client?

Here is the log...

2016-01-11 21:58:53 INFO: FIM server 0.6.0 (based on NXT 1.5.10) started successfully.
2016-01-11 21:58:53 FINE: Known peers: 22
2016-01-11 21:58:53 INFO: Copyright © 2013-2015 The Nxt Core Developers.
2016-01-11 21:58:53 INFO: Copyright © 2014-2015 Krypto Fin ry and the FIMKrypto Developers.
2016-01-11 21:58:53 INFO: Distributed under GPLv2, with ABSOLUTELY NO WARRANTY.
2016-01-11 21:58:53 INFO: Client UI is at http://localhost:7886/index.html
2016-01-11 22:00:12 FINE: Forger 565710271052013746 deadline 501 hit 66792797 started
2016-01-11 22:00:56 FINE: Database connection pool current size: 3
2016-01-11 22:01:49 FINE: Got 1 confirmations
2016-01-11 22:01:49 FINE: Downloaded 719 blocks
2016-01-11 22:01:49 FINE: Forger 565710271052013746 deadline 473 hit 66822423
2016-01-11 22:01:49 FINE: Account 565710271052013746 generated block 3809639243991647299 at height 911890 timestamp 67255289 fee 0.0
2016-01-11 22:02:03 FINE: Will process a fork of 359 blocks
2016-01-11 22:02:03 FINE: Rollback from block 3809639243991647299 at height 911890 to 355258507163840320 at 911889
2016-01-11 22:02:38 FINE: Database transaction required 16.463 seconds at height 912000
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:807)
  nxt.BlockchainProcessorImpl.lambda$new$15(BlockchainProcessorImpl.java:735)
  nxt.BlockchainProcessorImpl$$Lambda$4/13545776.notify(Unknown Source)
  nxt.util.Listeners.notify(Listeners.java:52)
  nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:1002)
  nxt.BlockchainProcessorImpl.access$500(BlockchainProcessorImpl.java:64)
  nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:463)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:448)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:194)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:123)
2016-01-11 22:03:26 FINE: Switched to peer's fork
2016-01-11 22:03:27 FINE: Got 1 confirmations
2016-01-11 22:03:27 FINE: Downloaded 359 blocks
2016-01-11 22:03:27 FINE: Forger 565710271052013746 deadline 492 hit 66840259
2016-01-11 22:03:28 FINE: Account 565710271052013746 generated block 5247592672911024894 at height 912249 timestamp 67255388 fee 0.0
2016-01-11 22:03:55 FINE: Will process a fork of 719 blocks
2016-01-11 22:03:55 FINE: Rollback from block 5247592672911024894 at height 912249 to 5778458484517274792 at 912248
2016-01-11 22:06:33 FINE: Switched to peer's fork
2016-01-11 22:06:35 FINE: Got 1 confirmations
2016-01-11 22:06:35 FINE: Downloaded 719 blocks
2016-01-11 22:06:35 FINE: Forger 565710271052013746 deadline 949 hit 66877846
2016-01-11 22:06:36 FINE: Account 565710271052013746 generated block 12998951752453693966 at height 912968 timestamp 67255575 fee 0.0
2016-01-11 22:06:58 FINE: Will process a fork of 719 blocks
2016-01-11 22:06:58 FINE: Rollback from block 12998951752453693966 at height 912968 to 5992997622055858393 at 912967

14
General FIMK Discussion / FIMK and Solu?
« on: October 16, 2015, 01:48:50 PM »
I saw this Finnish startup looking to reinvent personal/business computing.  They are using a subscription model for the software.  I wonder if they might be interested in using FIMK as a possible payment option.

http://www.solu.co/


15
FIMK Client discussion / Lompsa 0.4.10 Problem
« on: October 16, 2015, 03:37:32 AM »
I'm updating my test server code using the Lompsa 0.4.10 download (linux 32).  I take the contents of the FIM directory and copy over to my test server as I have always done in the past.  When I run the server, I get a database upgrade error.

Code: [Select]
2015-10-16 01:14:15 FINE: Will apply sql:
CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height)
2015-10-16 01:14:15 SEVERE: Database error executing CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height)
java.lang.RuntimeException: Database error executing CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height)
at nxt.db.DbVersion.apply(DbVersion.java:83)
at nxt.NxtDbVersion.update(NxtDbVersion.java:738)
at nxt.db.DbVersion.init(DbVersion.java:55)
at nxt.db.BasicDb.init(BasicDb.java:136)
at nxt.Db.init(Db.java:39)
at nxt.Nxt$Init.<clinit>(Nxt.java:339)
at nxt.Nxt.init(Nxt.java:313)
at nxt.Nxt.main(Nxt.java:300)
Caused by: org.h2.jdbc.JdbcSQLException: Table "VOTE" not found; SQL statement:
CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height) [42102-176]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
at org.h2.message.DbException.get(DbException.java:178)
at org.h2.message.DbException.get(DbException.java:154)
at org.h2.schema.Schema.getTableOrView(Schema.java:439)
at org.h2.command.ddl.CreateIndex.update(CreateIndex.java:61)
at org.h2.command.CommandContainer.update(CommandContainer.java:79)
at org.h2.command.Command.executeUpdate(Command.java:254)
at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:132)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:117)
at nxt.db.FilteredStatement.executeUpdate(FilteredStatement.java:45)
at nxt.db.TransactionalDb$DbStatement.executeUpdate(TransactionalDb.java:256)
at nxt.db.DbVersion.apply(DbVersion.java:74)
... 7 more
2015-10-16 01:14:15 INFO: Shutting down...

Previously, my server code was 0.5.1 (from Lompsa 0.4.8 download).  It looks like that somewhere the code didn't create the "vote" table.  Was that done in the Lompsa 0.4.9 release? 

Pages: [1] 2 3