Author Topic: FIMK 0.4.0 - Everybody update please  (Read 8000 times)

Dirk Diggler on: March 20, 2015, 07:08:39 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Please everyone update your nodes to 0.4.0 so we can enable the hard fork and get rid of the public key requirements.
This is the server package, the client package (MofoWallet) will follow in a couple of hours.

http://fimkchat.com/2015/03/fimk-server-0-4-0-mandatory-update/


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 /$$$$$$$$ /$$$$$$ /$$      /$$          Release : 0.4.0         
| $$_____/|_  $$_/| $$$    /$$$          Date    : 2015-03-20         
| $$        | $$  | $$$$  /$$$$                 
| $$$$$     | $$  | $$ $$/$$ $$          http://fimk.fi       
| $$__/     | $$  | $$  $$$| $$          http://mofowallet.com
| $$        | $$  | $$\  $ | $$          http://forum.fimk.fi         
| $$       /$$$$$$| $$ \/  | $$          https://github.com/fimkrypto/mofowallet
|__/      |______/|__/     |__/                 
                     /$$                                       /$$             
                    | $$                                      | $$             
                    | $$   /$$  /$$$$$$  /$$   /$$  /$$$$$$  /$$$$$$    /$$$$$$
                    | $$  /$$/ /$$__  $$| $$  | $$ /$$__  $$|_  $$_/   /$$__  $$
                    | $$$$$$/ | $$  \__/| $$  | $$| $$  \ $$  | $$    | $$  \ $$
                    | $$_  $$ | $$      | $$  | $$| $$  | $$  | $$ /$$| $$  | $$
                    | $$ \  $$| $$      |  $$$$$$$| $$$$$$$/  |  $$$$/|  $$$$$$/
                    |__/  \__/|__/       \____  $$| $$____/    \___/   \______/
                                         /$$  | $$| $$                         
                                        |  $$$$$$/| $$                         
                                         \______/ |__/ 

This is the FIMK server package, while you can run this on your computer it's
not intended as such. Users of the FIMK server package generally install it
on a server.

For people looking for the installable FIMK client please check out our
desktop client dubbed MofoWallet which can be found at our github repo which
is here https://github.com/fimkrypto/mofowallet/releases.


 

FIMK 0.4.0 is based on NXT 1.4.13 (plus the critical parts of 1.4.16)

This is a hard fork everyone MUST update to this release. The hard fork will go
into effect the moment we set an alias that enables new accounts without public
key to receive FIMK.

On first startup a series of changes will be performed on the database, these
changes are quite extensive and might take a while to complete. Just let it run
and FIMK will start when it's ready.

* Fixed the recent forking issues

* Upgraded to NXT 1.4.13/16 (most recent NXT release)
 
  Tons of upstream (NXT) security updates and general improvements.
 
  - Improvements in exception handling, transaction validation, error logging.
  - Prevent server from starting if any of the startup tasks failed.
  - Avoid unnecessary DNS queries.
  - No longer process or return "comment" parameters in Asset Transfer.
  - Stores all derived objects in the database, instead of keeping all of them
    in memory only.
  - Startup time is now reduced to a few seconds only.
  - Everywhere, object ids that used to be Longs are now primitive longs.
  - Preserve and re-process unconfirmed transactions after fork resolution
    pop-off.
  - Improved propagation of unconfirmed transactions.
  - Multiple minor improvements and optimizations based on profiling results.
  - Updated to latest Jetty version
  - Allow re-broadcasting of transactions already in the unconfirmed pool.
  - Show correct timestamps in asset transfer history.
  - Only try to set account public key when inside a database transaction,
    fixes a bug in setting public keys for accounts that never had an
    outgoing transaction.
  - Improved default H2 cache size allocation.
  - Disabled the SSLv3 protocol when using SSL for the API.
  - Fixed incorrect guaranteed balance bug in getAccountLessors API.
  - Cache hallmarked peer account balances to reduce number of database calls.
  - Other minor performance improvements and bugfixes.
  - Fixed decryption of purchased DGS goods.
  - Fixed missing DGS purchase feedbacks.
  - Implemented full text search using the Lucene library, as supported by H2.
  - Show purchase counts and public feedback counts in all API responses
    returning Goods JSON, unless includeCounts parameter is false.
  - Increased default purchase delivery deadline to 168 hours (1 week).
  - Include full peer info in getPeers API if includePeerInfo=true, to avoid
    having to do a separate getPeer request for each peer.
  - Allow transaction signing in signTransaction to skip the validation of the
    transaction bytes being signed, if an optional validate=false parameter is
    added.
  - Allow sending messages with no recipient.
  - Automatically blacklist peers with version older than 0.3.3
  - After the Monetary System block, the order in which transactions in a block
    are executed will be determined by the block forger, instead of by id,
    default being by arrival time at the forger's node.
  - Improvements in blockchain download to prevent getting stuck on the wrong
    fork.
  - Nodes will download blocks in batches of not more than 719 blocks at a time
    from a single peer, and after each such batch will verify  with
    nxt.numberOfForkConfirmations other peers (default 5) if this is the best
    fork, before continuing, unless the downloaded batch is of less than 10
    blocks.
  - Rescan status is now saved in the database, to prevent the database from
    being left in an inconsistent state when a rescan fails or is interrupted.
    Once a rescan has been scheduled, it will be triggered again at restart,
    until it completes successfully.
  - Improvements in the processing of unconfirmed transactions.
  - Fixed currency decimals issue.
  - Fixed minor bugs in MS transaction validation.
  - Additional validations of Monetary System transactions, and bugfixes
    in existing validations.
  - Bugfixes in currency minting and in MintWorker.
  - Improved peer networking to run the sending of blocks and transactions
    to peers in a background thread.
  - Do not log currency exchanges of zero amount.
  - Fixed setting of peer state. Improvements in connecting to peers.
  - Enforce that currency exchange offer expiration height is after the current
    blockchain height.
  - The Message Pattern in AccountInfo feature, introduced in 1.4.0e, has been
    disabled, and will not be activated. This is to prevent
    possible denial of service attacks by malicious regular expression patterns
    which can cause excessive CPU load with certain inputs.
  - Enhanced nxt.allowedBotHosts property to also accepts a range of addresses
    using CIDR notation.
  - Allow no more than one unconfirmed minting transaction per account and minted
    currency to be accepted in the unconfirmed pool.
  - Better validation of hallmarks for peers with multiple addresses. Do not
    blacklist peers with invalid hallmarks but just treat them as not hallmarked.
  - Minor peer networking improvement, addPeers and processBlock requests are now
    executed in the background.
  - Improvements in fork resolution. The peer networking getNextBlocks API no
    longer limits the number of blocks returned to 1 MB total payload size,
    but always returns 720 blocks, if available.
  - Fixed a bug in transaction bytes parsing which could cause signature
    verification failed errors and break forging.
  - When downloading the blockchain, require at most one fork confirmation when
    still below the last hardcoded checkpoint.
  - Peer port handling has been improved to allow different peers to share the
    same IP address provided they use different ports.
  - To prevent overloading a node with invalid peer addresses, the maximum total
    number of known peers is limited to nxt.maxNumberOfKnownPeers (default 2000).
    Once this number has been reached, new peer addresses are not added, and peers
    that have been last connected to more than a week ago are removed from the known
    peer list, provided the node has enough connected public peers, until the number
    of known peers is again reduced to below nxt.minNumberOfKnownPeers (default
    1000).
  - Improved database performance by storing currency supply and reserve per unit
    data in a separate table.
  - Fixed a bug in transaction validation that could break blockchain downloading.
  - The default (and minimum allowed) value for nxt.maxRollback is now 1441.
  - Restrict maximum HTTP request and response size in peer networking to prevent
    potential out of memory attacks.
  - Improved fork resolution by allowing a better difficulty block pushed from a
    peer to replace the current last block.
  - When forging, do not accept a peer block with hit time after the next hit time
    of a currently forging account (i.e. prevent front-running in forging).
  - Removed the possibility of a forger to miss his turn. Even if late, the block
    will still be generated and submitted.
  - Delay forging and submission of blocks by 20 s, configurable via the
    nxt.forgingDelay property, in order to be able to accumulate more transactions
    in the forged block. The arrival of a front-running block from a peer however
    cancels that delay and the next block is generated up to 3 s earlier instead,
    which can be controlled via the nxt.forgingSpeedup property.
  - Better logging of peer networking errors. Log, but do not blacklist missing or
    malformed JSON responses.
  - Database optimization. Moved the public key of accounts, transaction senders,
    and block forgers to a separate table, resulting in 15% reduction of total
    database size.
  - Enforce that the nxt-default.properties file used matches the version of the
    current release.
  - Peer networking improvements, better logging, bugfixes.

* The NXT client (known as wesley client) has been removed from the FIMK server
  package. A slimmed down single currency (without NXT support) version of
  the FIMK client (aka MofoWallet) has replaced it.
 
  If people want the old client back they can copy it back from the FIMK 0.3.3
  release. You should copy the entire 'html' folder from 0.3.3 and move it to
  FIMK 0.4.0. Then in nxt.properties set 'nxt.apiResourceBase=html/ui'.
 
  We will no longer do work on the old client.
 
* FIMK now has an embedded WebSocket server, it's separate from the existing
  API server.
 
  The WebSocket protocol is an improvement of the more than 25 year
  old HTTP protocol. WebSockets are faster, more efficient and allow for
  two-way communication.
 
  See these posts for background information:
 
  http://fimkchat.com/2015/03/connecting-to-fimk-websockets/
  http://fimkchat.com/2015/03/fimk-adds-websocket-support-to-its-core/
 
* New functionality for FIMK is now exposed as asynchronous RPC calls accessed
  over the WebSocket server.
 
  Because of the two-way communication abilities of WebSockets now RPC calls
  can be created that do work in a background thread on the server and will
  notify the client when they are ready. Meanwhile the server and client can
  be used as normal.

* The old API server is turned off by default. If you need to access it you can
  enable it in nxt.properties through 'nxt.enableAPIServer=true'
 
* A bridge exists in the callFunction RPC to call any old API method by name,
  the old API calls are accessed from memory so no need to actually run/start
  the API server (saves memory/cpu).
 
* Tons of new RPC calls, each one tailored to support a different aspect of the
  FIMK client (aka MofoWallet).
 
  List of new RPC calls (WebSocket API).
 
  - CallAPIFunction 
    Call any old API calls in the old HTTP API server. We support each call
    listed here http://wiki.nxtcrypto.org/wiki/Nxt_API. It is not necessary
    for the API server to be running.   
 
  - GetAccount 
    Returns the account balance, name and some other account related things.
 
  - GetAccountAssets 
    Allows to paginate through list of account owned assets. Asset data always
    includes the asset name, decimal places etc for easy access on the client.
    Pagination is index based.
 
  - GetAccountCurrencies 
    Allows pagination through all currencies owned by an account, currency
    details are always included.
    Pagination is index based.
 
  - GetAccountPosts 
    Allows to paginate through all POSTS written by an account.
    POSTS are stored in the mofo_post database table.
    Pagination is index based.
   
  - GetAssetPosts 
    Same as account posts but works for asset posts
   
  - GetComments 
    Allows to paginate over comments for account and asset posts.
    Pagination is index based.
   
  - GetCommentCount 
    Returns the number of comments for a post.
 
  - GetAccounts 
    Returns balances for multiple accounts
 
  - GetActivity 
    Returns blocks, transactions and trades. This extensive RPC call can be used
    to return all trades + transactions spanning a selection of blocks. Supports
    a filter mechanism to query for transactions based on time and on a range
    of transaction types.
 
  - GetActivityStatistics 
    Returns network statistics, average block time, block rewards per day, week
    month.
   
  - GetAskOrder, GetBidOrder 
    Returns an ask/bid order.
   
  - GetAsset 
    Does what it says
   
  - GetAssetChartData 
    There is a listener that listens trades in blocks. The asset prices are
    bundled per hour, 3 hour, day and week to get a moving average and open,
    close, high, low and average prices.
    These moving averages (and open/close etc) are stored in a new table in the
    database and this RPC accesses that data.
 
  - GetAssetOrders, GetAssetTrades 
    Does what it says. Pagination is index based.
   
  - GetBlockchainState 
    Minimalist blockchain state includes only height and timestamp.
   
  - GetForgingStats
    Allows paginating over the list of top forgers for the past 24 hours.
    Pagination is timestamp based.
   
  - GetMyOpenOrders
    Allows paginating over all open orders but for a list of accounts.
    Pagination is index based.
 
  - GetRecentTransactions
    Returns recent transactions (includes unconfirmed) for a list of accounts.
    Supports the same filter mechanism as GetActivity RPC.
    Pagination is index based.

* New feature.. Write POSTS/BLOGS linked to an Account or Asset. The POSTS are
  stored on the blockchain (for now) and are entered through AM (arbitrary
  messages). The AM format was chosen instead of a new transaction type in
  order to stay compatible with NXT and allow the functionality to be used in
  multi-currency MofoWallet client.
 
  The POSTS are stored in the database and are fully aware of blockchain reorgs.
 
  Note: POSTS are limited to accounts and assets but will be extended to
  currencies and goods on the goods store. 
 
* New feature.. Write COMMENTS to POSTS/BLOGS every account can leave a comment
  on each Asset or Account POST.
 
* Added tests for most new functionality

* Upcoming big feature PRIVATE ASSETS.

                             ~~~ DOWNLOAD ~~~

https://github.com/fimkrypto/fimk/releases/download/v0.4.0/fim-0.4.0.zip
 
SHA256 de58bc4a8b256e71bb3e9a37a066422e777d649c32d0f5838f5d5def6eb1d7a5
MD5    76a905741dd7954f80f485a11aa68459

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVDFTLAAoJEP9gzPcARnvnzwoH/i9TqpsXfM6WmYM8nHH2kpmP
p7MGFa26frJ7gSxxgrSsRE1gvexNmus1eibtZ+1LT/uIkch3Lm/Xph7QAnRH9h5s
cZ266Kz88pA4B3CadsOG5cbacLofQue2wyU+J4gwLrGqOF+owfob9w0rox+N03PM
qFNIoYn/mM/bTiKCXuBvktcph0Hu1ecTWSSojfNCfVq1H7O4ZLdQs1iWzKHMhUI3
PF+XunNyfwnzwD0lKIOH1LUk1PGzwmfpNPBcidQsS4/a3Jsk/2qv6krk6Gex40+v
ZndWR8cV6ZX0Xwnak30VCo7FW5yDo8y/W53dT5xizviahc1a4KROhUL8qxVTX0o=
=1uAF
-----END PGP SIGNATURE-----
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Dirk Diggler #1 on: March 20, 2015, 07:55:30 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
In order to enable the UI client on localhost:7886 please set nxt.enableAPIServer=true in nxt.properties and it will auto start on startup.
The client package (desktop client) will be the one to use if you are on a desktop computer. I'm preparing it's release now.

The reason the UI client is set to not start automatically is because it's planned that people will use their desktop client to connect to their private servers, however this switch in the desktop client is not available in the coming release. Hopefully i'll be able to add that in the coming week.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Espo #2 on: March 20, 2015, 10:40:43 PM

  • Fresh Fimker
  • *
  • Posts: 16
    • View Profile
Hey  :thumbup:
Thanks for the new release :)

I'm trying to understand the new options. Am I right the this:

Code: [Select]
# Host interface on which to listen for websocket/json API request, default localhost only.
# Set to 0.0.0.0 to allow the API server to accept requests from all network interfaces.
nxt.websocketServerHost=0.0.0.0

means that everyone who can connect to my server is able per default to connect my hostet mofowallet and can forge?
Sorry if my question is confusing.



Dirk Diggler #3 on: March 20, 2015, 10:48:47 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Hey  :thumbup:
Thanks for the new release :)

I'm trying to understand the new options. Am I right the this:

Code: [Select]
# Host interface on which to listen for websocket/json API request, default localhost only.
# Set to 0.0.0.0 to allow the API server to accept requests from all network interfaces.
nxt.websocketServerHost=0.0.0.0

means that everyone who can connect to my server is able per default to connect my hostet mofowallet and can forge?
Sorry if my question is confusing.

nxt.websocketServerHost has the same meaning as nxt.apiServerHost, if you set it to 0.0.0.0 you can connect to it from another machine. Looking at it now it might be better if we set it to localhost in the default config.

As for forging on your node, that is controlled by another setting. This one is FIMK specific (not available in NXT).

# For public nodes, only allow these accounts to forge.
# Values can be a ; delimited list of accounts, an empty value (for no forging allowed)
# or a * to allow all accounts to forge.
nxt.allowedToForge=*
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Espo #4 on: March 20, 2015, 10:55:15 PM

  • Fresh Fimker
  • *
  • Posts: 16
    • View Profile
Ahh ok,
Thanks for the fast answer :)

Zlotnik #5 on: March 21, 2015, 08:01:51 PM

  • Fresh Fimker
  • *
  • Posts: 14
    • View Profile
Noobie question here about new server version.
A: Is old db file compatible or do i need download it again instead of copying old data?
B: Does all info about server activity (like in monitoring in new MOFO wallet with server) are availible from UI level after activating it?

I prefer to use server + browser instead of wallet it consumes less memory and energy, is faster or i run it only for some time e.c.
I must always mess something up so just need confirmation if i understand all changes properly. Thx for hints how to make it work again ;)

Dirk Diggler #6 on: March 21, 2015, 09:30:09 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Noobie question here about new server version.
A: Is old db file compatible or do i need download it again instead of copying old data?
B: Does all info about server activity (like in monitoring in new MOFO wallet with server) are availible from UI level after activating it?

a. Yes it's compatible, the database will be changed in a big way so the update will take a while. After that a scan and validation is done of all transactions which also takes a lot of time.

b. The UI you get from server FIMK is a little bit different from for instance hosted FIMK (mofowallet) you for instance get the peer explorer added. But if in doubt just download and run it locally on your pc, no need to install it on your server right away.

I prefer to use server + browser instead of wallet it consumes less memory and energy, is faster or i run it only for some time e.c.

The desktop version is pretty fast now and doesn't use that much memory. If you just want to access your account then dont start the server (or check the box to never start the server). On my system it's started in a few seconds and i dont have a high end machine (or fast OS).
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Zlotnik #7 on: March 22, 2015, 01:29:01 PM

  • Fresh Fimker
  • *
  • Posts: 14
    • View Profile
I made it and it works properly just needed to wait a bit more. Yes it is faster and many interesting things have been added.

But it lacks some old stuff, quite basic, that i really enjoyed. It lacks informations about new blocks. Now i still see in transactions date when i started leasing my FIMKS and  for how many blocks but i can't see any information on which block it started, on which block it will end and on which block we actually are progressing to estimate how much time will pass to end of leasing... I think page balance leasing isn't finished? Or maybe i don't know where to check it.. yet?     

There's much more info about general network statistics and that's great. But i'm a bit lost in this interface. Need to use to it maybe.

Is it possible to use old interface and check difference and old blocks statistics? I see option to enable it in nxt default properties but i still get new interface in browser at port 7886. How could i get back to old stuff for a moment?

Polarpanda #8 on: March 22, 2015, 01:58:49 PM

  • Fimker
  • **
  • Posts: 70
    • View Profile
My question is: Where is the little green light showing if you are forging or not, while running local server fim-0.4.0? Or more broadly, where can I see my forging status from the browser?

Could you could add a colored filled circle & a little text in default Mofo Wallet layout representing something like this:

1: white - doing nothing
2: green - forging locally - with number of block forged
3: orange - leased out with the estimated time to end (in human understandable form)
4: red - leased out with auto renew (for example 24h at a time if there is a technical reason it can't be shorter )

It wouldn't take much space and might be useful?

Now if I go to a link Explorer->Forgers, I get a list of what? I have forged blocks before but I'm not on that list so what does this list represent?
 
In my case leasing would be great if it was automatically extended until user decides to stop it. What is the point of measuring lease time in predefined number of blocks,  other than a technical reason?


Dirk Diggler #9 on: March 22, 2015, 09:18:08 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
I made it and it works properly just needed to wait a bit more. Yes it is faster and many interesting things have been added.

But it lacks some old stuff, quite basic, that i really enjoyed. It lacks informations about new blocks. Now i still see in transactions date when i started leasing my FIMKS and  for how many blocks but i can't see any information on which block it started, on which block it will end and on which block we actually are progressing to estimate how much time will pass to end of leasing... I think page balance leasing isn't finished? Or maybe i don't know where to check it.. yet?     

There's much more info about general network statistics and that's great. But i'm a bit lost in this interface. Need to use to it maybe.

Is it possible to use old interface and check difference and old blocks statistics? I see option to enable it in nxt default properties but i still get new interface in browser at port 7886. How could i get back to old stuff for a moment?

If you want to get back the old UI the only way would be to copy back the contents of html folder from FIMK 0.3.3 to FIMK 0.4.0 and set "nxt.apiResourceBase=html/ui" in nxt.properties.

I'm planning on doing some more blog posts on general usage, I can imagine it's not as straight forward as i wish it would be.

But on the other hand to fit everything in a limited sized screen and make it somewhat intuitive is probably not possible while keeping in-tact all the rules for the old client.

You are right about the information you are missing, thats all planned and will be added.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Dirk Diggler #10 on: March 22, 2015, 09:27:24 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
My question is: Where is the little green light showing if you are forging or not, while running local server fim-0.4.0? Or more broadly, where can I see my forging status from the browser?

Could you could add a colored filled circle & a little text in default Mofo Wallet layout representing something like this:

1: white - doing nothing
2: green - forging locally - with number of block forged
3: orange - leased out with the estimated time to end (in human understandable form)
4: red - leased out with auto renew (for example 24h at a time if there is a technical reason it can't be shorter )

It wouldn't take much space and might be useful?

Now if I go to a link Explorer->Forgers, I get a list of what? I have forged blocks before but I'm not on that list so what does this list represent?
 
In my case leasing would be great if it was automatically extended until user decides to stop it. What is the point of measuring lease time in predefined number of blocks,  other than a technical reason?

There should be an indicator that your account is forging. I even added a new API for that so you no longer needed to send your passphrase to the server to check that. The problem however is that the indicator is not properly hooked up yet to the server side events (websockets) so at the moment you need to navigate away to another page and come back to your account page before you will see the spinning wheel which indicates it is forging.

Right now it's a blue spinning icon next to the avatar on the pulse page of your account, but the colors you propose would work even better.

> Forgers

It's the top-ranking of the past 24 hour forgers. I figured people would want to be able to quickly see if their node is still producing blocks and how many when compared to others.

> Leasing

This has not had enough attention and is a the bare minimum stage right now.

The amount of code added for Mofowallet and FIMK 0.4.0 was quite a lot, now that we shipped most of it is the time to go over details like the ones mentioned by you. But please keep em coming, two minds are better than one, three are better that two I remember someone wise telling me once.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

farcurlew #11 on: March 22, 2015, 09:49:33 PM

  • Fresh Fimker
  • *
  • Posts: 15
    • View Profile
Hello
Everything on the linux desktop version looks ok and shows my account balance.

But when I run this on a VPS, I can access it through an ssh tunnel, but my account is empty?

It shows the same account as on the desktop version but it is empty.

How do I know if I am forging with this new version?

Espo #12 on: March 23, 2015, 10:44:18 AM

  • Fresh Fimker
  • *
  • Posts: 16
    • View Profile
Hmm i think you have to tunnel two ports: 7886 and 7986.
Or how are you tunneling?

farcurlew #13 on: March 23, 2015, 02:25:33 PM

  • Fresh Fimker
  • *
  • Posts: 15
    • View Profile
Hmm i think you have to tunnel two ports: 7886 and 7986.
Or how are you tunneling?
From the local workstation on port 7886 to the VPS on 127.0.0.1:7886.

It has worked since day one, now it doesn't. It sucks. I have been forging since day 1 and now I cannot.

Zlotnik #14 on: March 23, 2015, 02:36:16 PM

  • Fresh Fimker
  • *
  • Posts: 14
    • View Profile
>Leasing time count

Luckly i found a way by getting to know better interface. You just check leasing transaction details to add up manually block height and period - blocks of leasing - getting this way nr of block when leasing is ending while actuall block height i simply in Explorer > Blockchain tab. The only thing i miss in new wallet now is that social tab with updates on forum but it isn't so much essencial (and might be in plans on bigger scale or in different form). I guess we should focus on discovering all new stuff already done first.   

Thanks for details how to run old interface i'll try it out some other time.

Hmm BTW a different question. If i'm leasing account to forging pool which didn't update server to newest version yet is that affecting in any way leasing results or does blocks are forged there as usually?