Avoiding fork mechanism

Maybe it can be noob question but i want to know how it works.

I ask again and again on slack, but i cannot understand.

I want to know how lightweight contract avoiding fork by using ecparameters.

For example, when i send ignis to Tarasca account on height 1000 , they send card on height 1001. No need to consider fork because they use lightweight contract.

When a contract is invoked by a transaction, like your example above, it can produce one or more output transactions. Those transactions are sent linked to the trigger transaction using the referenced transaction field.

From the Create Transaction docs:

referencedTransaction creates a chained transaction, meaning that the current transaction cannot be confirmed unless the referenced transaction is also confirmed

Remote api cannot make referenced transaction ?

Yes, they can. You just use the referencedTransaction parameter I pointed out above.